Dashboard

Pricing

A credit is Simmit's unit of compute, and credits are sold at a flat $40 per million. Sims are metered per second of SimC runtime at your account's metering rate: at 51 credits per second, a job that finishes in ten seconds costs 510 credits. The rate tracks the speed of the machine your sims run on, so on faster hardware a sim finishes sooner at about the same total cost. See Credits⁠ (opens in new tab) for exactly what each job is metered on.

Free monthly tier

New accounts start with one-time starter credits to test against. Verifying your account adds a monthly credit grant on top, at $0. Each sim is a compute job Simmit pays for; the account verification is the guardrail that lets the monthly tier exist. Your balance is shown in your Credits activity.

Credit packs

PackCreditsPrice
Starter125,000$5
Small250,000$10
Medium500,000$20
Large1,000,000$40

The price is flat: $0.00004 per credit at every pack size. A Starter pack covers about 41 minutes of sim runtime at 51 credits per second.

More capacity

Every account runs under limits: how many jobs it can have in flight, how much one job can spend, and how long a job can wait in the queue. Your current limits are on your account page. If you need higher concurrency, batch workloads, longer queue windows, reserved capacity, or invoicing, that's a Custom plan; get in touch.

What you're paying for

You're metered on SimC runtime and nothing else, rounded up to the whole second. Queue time, worker setup, orchestration, and result upload aren't metered, and idle capacity between jobs is Simmit's to pay for.

The rate is what keeps that capacity there: machines available when your job arrives, maintained and running current SimC builds. A 32-vCPU machine you run yourself costs a few hundred dollars a month, even on spot pricing, and that bill keeps running whether it's simming or not. Here you only pay while your sims run. Unless your project keeps a machine simming more than a couple of hours a day, Simmit costs less, and there's nothing to build first: no job queue, no VM scaling, no SimC builds to keep current. You pay for the sims, not the infrastructure.

By default, sims bill the account that submits them. If you're building a tool you want to keep free to run, each of your users can bring their own key so their sims bill their account instead; see Pass-Through Billing⁠ (opens in new tab).

Back to Help