Ryniant raises $300k at a $2.5M valuation, led by Verdict Capital

Security and IP

Your clients' structures are your clients' IP. We build like it.

When your client asks where their molecule went, you need an exact answer and a contract to point at. That is the requirement we build against.

other tenantother tenantYOUR WORKSPACEStructuresโœ“Routesโœ“Notebook (ELN)โœ“
Nothing crosses the boundary

The core commitments

Single tenant

Your structures, routes, and notebook data sit in an index only you can query. Nothing is pooled across customers.

Never training data

We do not train models on your data. Model calls run under a zero-retention agreement with a named, disclosed subprocessor, so prompts and outputs are not retained or trained on.

You own everything

Inputs, outputs, routes, and reports are yours. We take no license beyond what is needed to run your job.

Isolation across clients

A client's documents inform that client's jobs only and never cross to another client's work inside your workspace.

Deletion and audit

Every job logs what was retrieved and what it cited. Data is deleted on request and certified deleted at contract termination.

Deployment options

Three ways to run Ryniant, honest about the tradeoff of each. Select one to see where the boundary sits and what, if anything, leaves it.

YOUR TENANT ยท OUR CLOUDRyniant runtimeYour structures + ELNnothing leaves

An isolated tenant per customer. Fastest to start.

Your notebook, specifically

Your ELN stays in your environment. It is used only to inform your own jobs, never to train a shared model, and never exposed to another customer. Every recommendation drawn from it cites the exact entry, so nothing is a black box.

How a run is traceable

Every agent run records the context it saw, the tools it called, the sources it retrieved, and the citations behind each claim. A chemist or an auditor can reconstruct exactly why the system did what it did, and every decision is logged.

Where we stand on certifications

We are building toward SOC 2 Type II; the architecture is designed to support it, and we will state it here when it is complete. Model calls use a named subprocessor under zero-retention terms rather than implying no third party is involved. We do not claim HIPAA, GxP, or other regimes that do not apply to this product today.

Have your security team review the details.

We are glad to walk your security or legal reviewers through the architecture, the subprocessor terms, and the deployment that fits your perimeter.