Buying credits
Monthly Paid credits expire at billing-period end without rollover. Free credits expire at UTC month end; unused Free credits end when a Stripe Paid period starts. Monthly credits are spent before top-ups. Top-ups, automatic recharges, and signup, referral and bonus credits never expire, also not after a downgrade to Free. Only effective Paid workspaces can buy top-ups or enable automatic recharge, but bought credit stays usable after a downgrade.
An unpaid Stripe renewal retains Paid features for up to fourteen days after period end. Payment within that window continues coverage; otherwise Paid ends when the window ends and the workspace returns to Free, keeping its top-ups. Cancellation ends Paid at the paid period end, and
paid_until in ohmyhost credits account includes the renewal grace. Automatic recharge requires the workspace Owner’s consent and a gross monthly limit. Purchases and recharge.
A larger top-up changes the credits you receive, not consumption rates. Within one checkout, the portion above USD 100 grants 125 instead of 100 credits per dollar: 25% more. Ten USD 10 packs grant 10,000 credits; twenty grant 22,500.
Flag and referral credits
While at least one project shows the opt-in “Powered by ohmyho.st” flag, each Paid period you pay through Stripe adds 250 credits once per workspace, however many projects show it; granted and referral Paid days add none. That gives 1,250 instead of 1,000 monthly credits, 25% more. A flagged project’s custom hostname costs no credits on any plan (Connect a domain). Every workspace also has a referral link:ohmyhost referral link --organization "$ORGANIZATION_ID" --json, MCP referral_link_get, or Refer and earn in the portal account menu. A new user whose first workspace comes from your link, or from your flag while it still shows, starts with 1,000 credits and thirty days of Paid. That workspace’s first payment gives your workspace 1,000 credits and thirty more days of Paid unless a Stripe subscription or an unbounded grant already covers it. Referral credits never expire. A referral recommends ohmyho.st; it does not add someone to your existing workspace.
Become an affiliate for the signup prompt, your personal code and link, and the optional flag setup.
Usage rates
The table is generated from the same price contract as the website. Credits are the charge for the stated quantity, not a flat charge every time a feature is enabled. Usage is valued at the rate in effect when it happened.ohmyhost credits balance --organization "$ORGANIZATION_ID" --json (MCP organization_credits_get) reports active meters and their versioned rate cards; historical published cards can include meters that no longer charge usage.
Builds use the measured seconds of the current build sandbox. The historical CodeBuild minute rate is no longer used. A deployment reserves 16.86912 credits for 840 build seconds; after the build, only measured seconds are charged and unused reserved credits are released. A deployment that ends before its build starts releases the entire reservation. Starting the sandbox is not billed.
Database usage is selected RAM multiplied by active time: 256 MiB, 512 MiB, 1 GiB, 2 GiB and 4 GiB cost 10, 20, 40, 80 and 160 credits per active hour, prorated. Free supports 256 MiB with 500 MiB total disk; larger sizes require Paid and include 1, 2, 4 or 8 GiB disk. Total disk includes PostgreSQL/WAL overhead. Seven-day backups are included, with no separate database CPU, network or connection charges. After 300 idle seconds the database sleeps and incurs no active-RAM charge. Customer files and retained Worker resources keep their separate rates. Isolated Dev/Prod databases are metered independently; shared data uses one area. Inspect or change database capacity. Older rate cards can still list meters of the retired previous database provider (
neon.*); they describe historical usage only and never apply to a PGCF database.
Functions and crons use the Worker request and CPU meters. Workers bandwidth and SQL exports have no separate charge. Each deployment or promotion that goes live retains an immutable script for rollback; every retained script is charged at wfp.script, so its total grows with deployments even without traffic. Scripts remain until project deletion, or until a Dev reset/share action removes Dev-only scripts. mail.sent is charged per sent recipient and mail.received per received message; webhook retries do not add another mail charge.
Read charges correctly
One credit is 1,000,000 microcredits. Charges round up to the next microcredit with no minimum charge. Displayed rounding never changes the deduction. A zero-provider-cost unit has no credit charge; shared provider allowances do not create a separate customer allowance. Build and mail settlement is usually immediate or within minutes. Worker usage arrives about two to three minutes later, database usage is settled per hour, no earlier than two hours after that hour ends plus provider finalization and processing time, file operation usage about one to two hours later, and retained-resource charges can arrive after the UTC day closes. A current balance is not a final invoice for work that is still running. A balance never becomes customer debt. A zero balance starts one seven-day credit grace period; if it ends without new credits, the projects’ Dev and Prod URLs answer HTTP 402Project execution paused until credits are available again. This is separate from the fourteen-day unpaid Stripe renewal window. Read measured usage and set project budgets.