Registration takes two minutes — name, email, password, institution. Choose the "Continue with Google" option if your institution uses Google, and you never have to manage another password.
Verification and account access
Accounts are created immediately and you can sign in, explore and run work right away — there is no admin approval queue and no waiting for someone to review your signup. On deployments where card verification is enabled, work creation is gated only after the grace period shown in your billing settings (default 7 days) and unlocks with a $0 card check: a Stripe SetupIntent that proves the card is real and charges nothing. Some card networks place a brief $0–$1 authorization hold that auto-releases. Paid subscribers are already verified by billing, and on instances where verification is not configured the platform is fully usable without a card.
Compute credits and plan tiers
Compute is metered in credits: one credit ≈ one second of medium-weight compute (backend/core/credits.py). Each plan defines a monthly credit allowance — what you can spend that month — plus a weekly cap and a per-hour spend cap that smooth bursts. One-time credit packs raise the current month's allowance; they do not recur.
Four self-serve plans ship today: Free, Starter, Pro and Enterprise. Every plan includes the full pipeline — limits reflect real infrastructure capacity, not artificial feature caps. The Pricing page renders the live numbers (allowance, weekly cap, jobs per hour, concurrency, dataset size, storage and more) from the same billing catalog the server enforces; Settings → Billing shows your own usage.
Quotas reset on different windows: jobs per hour is a rolling hour, the weekly credit cap resets each ISO week, the monthly allowance resets each calendar month. When a request is rejected with HTTP 429, the message names the limit that was hit and when it resets. Running out of credits returns HTTP 402 instead — top up a pack or upgrade.