Tier 1 / Pilot
One application, one jurisdiction. For providers and vendors.A scoped, sovereign deployment for assessment. Single jurisdiction, single application, time-boxed, fully sealed, signed off in 30 days. The entry point for both audiences.
04 / ACCESS
Three engagement tiers.
Two audiences. One platform.
Bifrost operates The Keep, the sovereign AI stack, as a managed platform, sold direct and contact-led. Healthcare providers engage to build their own clinical applications on it. Software vendors engage to ship sovereign AI inside the products they sell. Every engagement starts with a Solutions Architect and a named operator team for the life of the relationship.
Three engagement tiers.
The Keep underneath all of them.
Tier 2 / Production
Multi-region, full catalogue, named Solutions Architect.The configuration nine of ten engagements run. Multi-region pairing, full catalogue of frontier open-weight models, dedicated Solutions Architect, regulator-direct evidence chain.
Tier 3 / Enterprise
Multi-site, multi-jurisdiction, multi-application.Master agreement covering multi-site, multi-jurisdiction, multi-application deployment. Dedicated tenant isolation, named operator roster, ministerial-level support. For health systems and the software vendors that ship into them at scale.
Pricing is scoped to the engagement, set with the Solutions Architect in discovery. No public price list, no per-seat meter.
Discovery to operation.
Bifrost runs the platform. You build the application.
Discovery.
One conversation with a Solutions Architect to scope jurisdiction, playbook, residency, and integration surface.
Sixty minutes. No deck, no demo theatre. The Solutions Architect surfaces the constraints the rest of the engagement will be designed around. The customer leaves with a clear view of what to build and on what.
Scoping.
Joint design memo. Playbook chosen. Substrate scoped. Compliance scope locked.
A single-page design memo signed off by both sides. Models version-pinned. Data residency confirmed. Integration patterns named. Evaluation harness defined. One business week. The build belongs to the customer; the design is jointly authored.
Build.
3verest provisions the sovereign substrate. The customer builds the application against the playbook. Assistance is available where useful.
Bifrost stands up the sovereign tenant, loads the curated models, exposes the RAG and inference primitives, and turns on the compliance evidence pipeline. The customer (or their software vendor) wires the integration, designs the workflow, and ships the application. Optional assistance covers prompt design, evaluation, and integration patterns. Thirty days from sign-off to first inference, typically.
Operate.
3verest operates the platform. The customer operates the application. The Solutions Architect accompanies the relationship for the life of the engagement.
3verest runs the substrate: deployment, model catalogue refresh, compliance evidence, observability, lifecycle. The customer runs the application: clinical content, workflow, user experience, change management. Quarterly performance review with the model catalogue refresh. Named operator coverage 24/7 on Production and Enterprise tiers. No tier-one queue.