Corvair CorvairKnowledge Substrate
arrow_backBack to the overview
The product

Run it your way, and prove it everywhere.

Corvair deploys in your cloud, on your own hardware, or as a managed service, with the outward-facing work in the cloud and your sensitive content held inside your firewall. It is licensed as a platform plus the domain content you choose, and it is secured for the decisions it is trusted to make, from identity to prompt injection to guardrails.

How you run it

Your cloud, your hardware, or our managed service.

The same software, deployed where your data and your regulators require it. Each customer runs an isolated installation, and an installation can host many knowledge bases.

Bring your own cloud
cloud

In your cloud account

A single-tenant installation in your own Google Cloud, AWS, or Azure. You hold the keys, the data, and the audit trail. The first build targets Google Cloud.

Inside the firewall
dns

On-premises or private cloud

The same software on your own infrastructure, for the most sensitive content and the strictest residency, with nothing leaving your network.

Fastest to start
cloud_done

Managed AI SaaS

Corvair-hosted and operated, multi-tenant for speed and economics, with every knowledge base private and segregated, so your content and its warrants are isolated from every other tenant. A dedicated single-tenant installation is available where physical isolation is required.

lan
Many knowledge bases, each private and segregated. Whether dedicated to you or hosted on the multi-tenant SaaS, every base is isolated, access is relationship-based and scoped per base, and a base can be physically isolated where required. Dev, test, and production are promoted by recipe, so what you tested is what you ship, and residency follows the region you choose.
Technical architecture

Two planes: outward discovery, your private knowledge.

The platform runs as two planes. The discovery and search plane reaches the open web, needs scale, and runs in the cloud. The knowledge plane holds your proprietary content, the knowledge store, the answers, and the warrant, and it can sit wherever your data must live: co-located in the cloud, on-premises, or in a private cloud. The two are joined by a narrow, governed seam: the knowledge plane pushes instructions out, the discovery plane returns its finds, and a steward admits them. Sensitive content never crosses outward.

shieldYour knowledge plane
Cloud · on-premises · private cloud
  • inventory_2Knowledge store and your proprietary content
  • forumAsk, Search, and the answers people and agents see
  • verified_userThe Validity Warrant and its signing key
  • account_treeSteward curation and the recipe
Stays where your data must live
arrow_forwardpush instructions
arrow_backpull finds
cloudDiscovery & search plane
Cloud, elastic scale
  • travel_exploreDiscovery: web crawl, news and site monitoring
  • searchExternal grounding and search over public sources
  • neurologyEmbeddings, ranking, and generation
  • scienceHeavy, elastic batch work
Outward-facing, no sensitive content
swap_horiz
The seam is one-way for data: instructions and queries go out, candidate sources and findings come back to be trust-scored and admitted in your knowledge plane. Because the plane is location-independent, the same design serves a cloud-hosted base, an on-premises base, or a fully air-gapped one that turns the outward plane off.
Security

Secured for the decisions it makes.

Authentication is the start, not the end. Because the substrate answers and acts on knowledge, it is hardened against the ways that answers go wrong: poisoned inputs, injected instructions, and ungoverned autonomy.

badge

Identity and access

  • loginSingle sign-on and OIDC, with least-privilege roles.
  • keyRelationship-based access scoped per knowledge base, not all-or-nothing.
  • smart_toyAgents act on scoped tokens under an explicit authority matrix.
  • lockNo static API keys; workload identity and managed secrets throughout.
privacy_tip

Data protection

  • coronavirusAll content is virus-scanned on ingestion before it is admitted.
  • visibility_offPII detected on ingestion and redacted, blocked, or allowed only under a declared, recorded purpose.
  • public_offResidency by region; isolation per customer and per base.
  • verified_userWarrants signed with a managed key, separate from the application identities.
  • historyEvery read and write recorded for audit.
security

Prompt-injection defence

  • document_scannerDocuments are pre-processed and screened for injected instructions on ingestion.
  • gpp_badAnything suspect is quarantined for review, not admitted to the base.
  • descriptionRetrieved content is treated as evidence with provenance, never as instructions to obey.
  • datasetAnswers are grounded in the governed base, not free browsing at answer time.
  • bug_reportPrompt-injection attacks are specifically tested for as part of every release.
  • fact_checkThe warrant records exactly what was used, so a manipulated source is visible after the fact.
gpp_good

Guardrails and oversight

  • blockNon-negotiable boundaries (regulatory, safety, policy) enforced in real time.
  • tollAgents run under circuit breakers and budgets that cap activity.
  • account_treeSeparation of duties: who asks, who curates, who runs the platform, who audits.
  • policyA complete, exportable trail for the second and third line.
Sovereignty & compliance

Your data and your compute stay where the law requires.

Regulated and public-sector buyers must answer not only where data lives, but where it is processed. Corvair addresses both, which is what makes a sovereign-cloud or on-premises mandate buildable.

public_off

Data sovereignty

Your content lives in the knowledge plane, in the region, on-premises site, or private cloud you choose, and never crosses the seam. Residency follows the region, and the outward plane carries instructions, not your data.

memory

Compute sovereignty

Processing and inference run where you require. The platform is model-agnostic, so answers can be generated by a model in-region or on your own hardware, the outward discovery plane can be pinned to a jurisdiction or switched off, and the warrant-signing keys stay in your control.

verified_user
Together this supports sovereign-cloud and on-premises mandates and aligns with the EU AI Act, GDPR, and national and sector rules, so a government or regulated buyer can keep both the data and the decision-making compute inside its border.
How it is monetised

A platform licence, the content you choose, and usage.

License the substrate and its virtual expert as a base, subscribe to the domain content you need, stand up additional knowledge bases, and pay for use as people and agents put it to work. A seat is one person or one agent.

payments
Land with one domain, then expand by seats, domains, knowledge bases, and usage. Adding any of them is a licensing decision, not a new deployment, because every virtual expert rides on the same substrate.
sellSee full pricing

See it run, then see how it sells.

The prototype shows the product in the hands of a user and a steward. The investor perspective shows the market, the model, and the moat.

desktop_windowsOpen the web app smartphoneOpen the mobile app trending_upInvestor perspective
arrow_backBack to the overview