Clear answers for process and engineering teams.

Acatian is a browser-based bioprocess engineering workspace. It connects process flowsheets, mass and energy balances, dynamic models, facility scheduling, CFD screening, TEA, LCA, source evidence, versions, and exports around one project model.

Process development uses it to design and scale routes; MSAT and manufacturing use it for tech transfer, scheduling and capacity; plant engineering uses it for equipment, utilities and facility concepts; TEA and LCA teams use the same process basis for cost and environmental decisions.

Batch, fed-batch, perfusion, continuous, and hybrid architectures can be applied to fermentation, cultivated products, biopharma, enzymes, alternative proteins, food processing, and related industrial biotechnology routes.

Yes. Use a customer-owned reference process, define acceptance tolerances, reconstruct the authorized process basis, and compare balances, schedules, economics, exports, and collaboration workflows before migrating any validated work.

The combined package includes the PFD, stream table, equipment register, mass and energy balances, reactions, parameters, ODE/PDE profiles, scheduling, utilization, TEA, LCA, uncertainty, sensitivity, sources, open boundaries, and missing validation tasks.

Yes. The modelling workbench checks degrees of freedom and initial conditions, executes operating procedures and events, fits parameters to experiments, runs Monte Carlo sensitivity, optimizes constrained decisions, reconciles online states, builds surrogate design spaces, and inspects distributed PDE domains.

Accuracy depends on model structure, inputs, calibration, and evidence. Acatian records low, base, and high values, units, sources, confidence, and validation state so screening results are not presented as validated plant predictions.

The in-app view is an interactive engineering screen for geometry, boundary conditions, transport risks, and external job preparation. Validated three-dimensional CFD requires a verified mesh, numerical settings, material models, convergence evidence, and an external CFD worker such as OpenFOAM.

No. It makes assumptions, dependencies, consequences, and missing evidence visible. Qualified engineers remain responsible for safety, GMP, regulatory, equipment, validation, and investment decisions.

Yes. Projects accept company-owned CSV and JSON data such as historian series, batch records, assays, recipes, schedules, utilities, TEA/LCA inventories, and supplier quotes. Mapping and preview steps show what changes before data is applied.

Team plans support projects, collaborators, invitations, branches, saved versions, comparisons, and audit records so changes can be reviewed and earlier states reopened.

Activated monthly subscriptions use Stripe-hosted Checkout. Stripe handles payment credentials; Acatian stores the customer, contract, plan, entitlement, and verified subscription status required to control access. When self-service checkout is unavailable, plan actions open a technical-pilot request instead.

Request a technical pilot for one process and one decision. The pilot defines inputs, model scope, outputs, acceptance criteria, and remaining validation work before a subscription or enterprise deployment.