Modeling on your own, or a team of you. Either way: no hardware, no maintenance contracts, and no surprises on the bill.
We’re onboarding a first group of consultants — “Request access” and we’ll set you up with your selections.
Individual
The complete modeling platform for one modeler. Compute is bought separately in packs — you only pay for machine time you actually use, and the hours you buy never expire.
One person, one workspace. Adding colleagues, shared projects and teams are Enterprise — they are not an add-on you can buy here.
See what’s includedEnterprise
For consultancies and organizations: several modelers working together, your own terms, and a person to call. We size compute to how you actually work rather than selling you a bigger tier.
Tell us what you need and we’ll come back to you. Nothing is charged and no account is created by asking.
One platform subscription. Compute bought in prepaid packs — hours that never expire. Storage metered by what you actually keep.
Step 1 · The platform
The complete modeling platform for one modeler. Compute is bought separately in packs — you only pay for machine time you actually use, and the hours you buy never expire.
Compute hours are not included — add a compute pack below, or start without one and buy hours when you’re ready to run.
Step 2 · Compute — buy hours once, use them whenever
Every model run, meteorology build, and screening check uses compute hours — one processor core working for one hour, measured from the machines’ own records. Buy a pack, and the hours land on your balance. Bigger packs cost less per hour.
Compute hours are a one-time purchase and never expire. They are not a monthly allowance: nothing is forfeited at the end of a month, there is nothing to roll over, and unused hours stay on your balance for as long as your account is open. Buy more at any time — packs stack.
What runs typically use
Compute hours measure machine work, not waiting time. Your run spreads across many machines at once — a study that uses 1,250 compute hours of work typically finishes overnight, because hundreds of machines each do a small piece simultaneously.
| Run | Compute hours billed | Approx. runtime |
|---|---|---|
| Screening run | under 0.1 | minutes |
| Meteorology processing (5 years of station data) | 0.2 – 0.5 | a few minutes |
| Standard facility run, 5 years of weather | about 0.5 | ~10 minutes |
| Mid-size study (≈25 sources × 10,000 receptors × 5 yr) | about 10 | ~30 minutes |
| Large facility (≈300 sources × 20,000 receptors × 5 yr) | a few hundred | a few hours |
| Full PSD cumulative run | about 1,250 | overnight |
Typical figures, shown to help you size a pack — they are not a guarantee. Actual compute use and time to results are determined by the model itself and vary with each project’s sources, receptors, weather years, and options. Every action shows on your usage page with the hours it drew from your balance, and we warn you while the balance is still comfortable. Running jobs are never interrupted — a job that starts, finishes.
Step 3 · Storage — metered, nothing to pick
The first 25 GB is included with the platform. Above that, storage is metered at $30 per TB-month, pro-rated by what you actually store — you are never asked to pick a tier, and there is nothing to outgrow. A standard run stores in about 10–20 MB; the largest cumulative runs about 1 GB, so most practices stay inside the free allowance for a long time. We never delete your data; everything is downloadable at any time, and if you cancel you get a 90-day read-only window to export before deletion.
Your selection
$150 / month platform
plus a one-time $150 for 1,000 compute hours that never expire · storage metered above 25 GB
Cancel the subscription anytime. Compute hours you have already bought are yours — they stay on your balance and never expire. Your usage page shows the balance, every run’s hours, and storage in real time.
Working with colleagues?