Биллинг

Skiffly is prepaid. A workspace has a balance in USD; the plan subscription and usage above what the plan includes are debited from it. There is no card on file and no invoice at the end of the month: when the balance is gone, services are paused after a grace period.

Plans#

The billing period starts on the day the workspace was created and runs one month. The subscription is debited once per period; usage is debited only after the period's gross usage exceeds the included amount. Plans are listed on Settings → Plans; switching from the dashboard is not available yet, write to support@skiffly.dev to change plan. Limits apply immediately after a change; the new subscription is charged from the next period.

Usage rates#

A month is 730 hours. Usage is sampled while a replica runs and charged to the balance every hour; a sleeping or paused service costs nothing except its volumes. Examples: a 512 MB / 0.25 vCPU web service is about $7.75 a month; an API (1 GB / 0.5 vCPU) plus Postgres (512 MB / 0.25 vCPU, 10 GB volume) about $24.50. The pricing page has a calculator.

Topping up#

Settings → Billing → Add funds. Presets $10 / $25 / $50 / $100, any amount between $5 and $1 000.

• PayPal: PayPal account or card at PayPal's checkout. The balance is credited when the capture completes.
• Crypto (NOWPayments): BTC, ETH, USDT, USDC and others; credited when the network confirms, usually within minutes. Partial payments are credited for the amount received.

The CLI shows the state with skiffly billing; the API has billingAccount, topupOptions, topupCreate(workspaceId, provider, amountCents) (returns a checkoutUrl) and ledger for the full history. Refunds through the provider are reflected as refund entries.

New personal workspaces receive a $5 trial credit once.

When the balance runs out#

1. Below $5 the dashboard shows a low-balance warning (billingAccount.lowBalance).
2. At $0 a 3-day grace period starts (negativeSince, pauseDueAt). Services keep running; usage keeps being debited, so the balance goes negative.
3. After the grace period every service in the workspace is paused: replicas are set to 0 and the deployments are removed. Volumes and data stay.
4. A top-up that brings the balance above zero resumes everything automatically: replica counts are restored and the services redeploy.

Auto-pause can be turned off (billingAutoPauseSet(enabled: false)); the balance then keeps going negative and you settle the debt with the next top-up.

Spend limit#

Set a per-period spend limit on the workspace (Settings → Billing, workspaceUpdate(id, input: { spendLimitCents })). When the period's gross usage reaches it, services are paused with reason spend_limit. Raising or removing the limit resumes them; topping up does not.

Auto top-up#

With PayPal you can save a payment method (Settings → Billing → Auto top-up; paypalAutoTopupSetup makes a first top-up and stores the method). Then, whenever the balance drops below the threshold (default $5), Skiffly charges the configured amount (default $20), at most once every 6 hours. autoTopupSet(enabled, thresholdCents, amountCents) adjusts it, paypalVaultDelete removes the saved method.

Where to look#

• Usage in the workspace sidebar: RAM, CPU, disk and egress per service for the period, and the projected bill.
• Settings → Billing: balance, ledger, payments, plan limits, pause state.
• skiffly billing, MCP billing-account, GraphQL usage(workspaceId).