How does billing work?
You top up a USD wallet and each job debits the actual cost of the compute it consumes. There is no subscription, no seat license, and no fixed tier. The whole pricing surface is one number, your balance.
Answers to the common questions about billing, accounts, data, and reading results.
You top up a USD wallet and each job debits the actual cost of the compute it consumes. There is no subscription, no seat license, and no fixed tier. The whole pricing surface is one number, your balance.
Yes. The minimum top-up is $20. Suggested amounts at checkout are $20, $50, $200, $500, and $2,500. There are no fixed packages, so you can top up any amount at or above the minimum.
When you submit a job, a hold is placed against your wallet for the estimated cost. When the job finishes, the final charge is settled against that hold. If the job ends up cheaper than estimated, the surplus returns to your wallet automatically.
No. There are no subscriptions, seats, or tiers, and no minimum monthly spend. You pay only for the compute your jobs use. Top ups are final and unused balance does not expire.
You are charged for the compute the job consumed, even on failure, because we pay our compute provider for that time. Per tool hard caps limit how much any single job can cost in the worst case.
The full billing model, example costs per tool, and the safety caps that prevent surprise bills are on the pricing page.
Sign up with your email at tools.ranomics.com. New accounts start with a small wallet balance so you can verify a tool works on your inputs before topping up.
Your uploads and results belong to your account and are tied to the email you signed in with. A job link opened under a different account will not show another user's results. See the privacy policy for the full detail.
Yes. Use a smoke run to confirm a tool accepts your inputs before committing to a paid run. It is the fastest way to catch a bad chain ID or a malformed PDB.
It depends on the tool and the scale you pick. A single ProteinMPNN inference finishes in about a minute. A pilot run on a generative tool typically lands between 15 and 45 minutes. Every tool form shows a typical runtime before you submit.
A design is one candidate the tool generates, a backbone with a sequence, scored and ranked against the others in the run. A pilot of about 8 designs gives a real first signal because roughly 1 in 5 passes the in-silico filter on a tractable target.
ipTM is interface confidence, higher is better, aim above roughly 0.7 on a tractable target. pLDDT is per-residue fold confidence, higher is better. i_pAE and pAE are predicted alignment error, lower is better.
From a finished job you can open any candidate in the 3D viewer and export the score table as CSV or the sequences as FASTA. Star the best candidates to build a shortlist for the wet lab.
Each per-tool guide explains what the tool is built for and how to read its output. The catalog compares them side by side.
If the docs do not answer it, email the team and we will help.