Priced relative to what a failed pilot run costs.

One simulation job = one upload + one scale-up prediction run. A bench-to-pilot job takes your bench run data and a target vessel spec, runs the FBA + kLa simulation, and returns a protocol output. If you re-run the same data with a different vessel geometry (e.g., comparing two impeller configurations), that counts as a second job. Strain comparison jobs that evaluate multiple variants from a single data upload count as a single job.

Yes. You can upgrade at any time, and we pro-rate the remaining months on the difference. If your scale-up campaign ramps up mid-year, you're not locked into underutilizing Starter through the end of your annual term.

The minimum input is a CSV file from your bench bioreactor run containing: time, OD600 (or DCW), dissolved oxygen %, pH, glucose concentration (g/L), and titer measurement (if applicable). Feed log (volume added over time) is required for fed-batch runs. The more measurement channels you provide, the tighter the flux model constraints and the more accurate the scale-up prediction.

We're in our first deployment cohort. Early access users get locked-in pricing for their first 12 months — meaning if we raise prices after the cohort fills, your rate doesn't change until your second annual renewal. We do this to make the economics clear: you're getting in before public availability, and the price you sign on at is yours for the first year.

Yes. Your uploaded data is processed within your private workspace and is never shared with other customers, used to train shared models, or accessed by Fermvyne staff except for support purposes when you explicitly request it. Enterprise customers can request a data processing agreement and on-premise deployment for complete data sovereignty. All data is encrypted at rest and in transit.

The four validated organisms (E. coli, P. pastoris, S. cerevisiae, F. venenatum) have pre-configured FBA models and have been tested against internal validation datasets. Other aerobic organisms can be supported at the Enterprise tier through a custom organism onboarding process — typically 4–8 weeks to validate against your experimental data and configure organism-specific overflow pathways. Contact us to discuss your requirements.