The enterprise runtime for production AI
The enterprise runtime for every Habitat we build. Your cloud. Auditable core. Run by the principals who built it.
Built for CISOs who have said "no" to AI rollouts and are looking for the "yes" that doesn't cost them their standards.
The Anatomy
A Habitat is the living environment for an agent. Not a wrapper around a prompt — a place where an agent exists. Persona, memory, tools, sessions, and sub-agents, all in one governed environment.
A Habitat contains
Persona
Who the agent is, what it will and won't do, its authority boundaries.
Tools
Typed interfaces to your SaaS, your databases, your internal APIs.
Memory
Persistent institutional knowledge. Facts the agent has learned, decisions it's made, edge cases it's handled.
And plugs into
Sub-agents
Specialized workers the Habitat delegates to. Composable, not monolithic.
Sessions
Every interaction logged, replayable, auditable. Your compliance team gets the paper trail.
Evals
Automated quality checks against known-good behavior. Regressions surface before production does.
The two-level model
Habitat OS is the enterprise runtime. A Habitat is the agent environment your team actually uses. Your monthly close Habitat, your hiring Habitat, your reporting Habitat — every one of them runs on Habitat OS.
Why Habitat OS
Banks, private equity firms, healthcare systems, and real estate operators have told us the same thing: they want modern AI, but not if it means giving up sovereignty over their data, their infrastructure, or their accountability chain. Habitat OS is the answer.
Deployed where you say
Habitat OS runs in your VPC, your dedicated cloud account, or our managed single-tenant environment. Customer-owned data stays customer-side. Model provider keys are yours to bring. On-prem is available case-by-case for regulated deployments.
Open at the core
The Habitat primitives — persona, tools, memory, sub-agents, evals — live in our open-source engine, Umwelten. Your security team can read every line. The enterprise distribution adds identity, observability, integrations, and human support.
Principal-led accountability
Every engagement is led by a named principal. No rotating analysts, no offshore handoffs, no layers between the people who understand your Habitat and the people fixing it when something breaks. Your CISO gets a direct line.
One platform, every Habitat
Your monthly close Habitat, your hiring Habitat, your executive reporting Habitat — all run on the same runtime, share the same identity layer, and benefit from the same operational tooling. Scale across departments without re-architecting each time.
Habitat WorkStreams · The human layer
Every Habitat on Habitat OS has a WorkStream layer — the place where your people actually work with it. Private by default. Promotable on their terms. Discoverable when the artifact is ready for the rest of the org.
The fast adopters stop racing away from the rest of the org. The skeptics get to watch before they participate. The work your best people do stops being lost when a tab closes, a laptop retires, or an employee moves on.
Private by default
Every employee gets a WorkStream. Their prompts, their artifacts, their workflows. Nothing is shared, seen, or indexed until they choose to promote it.
Promotable when ready
When a prompt actually works or a workflow is worth keeping, promote it to the team. Promote again to the org. The employee stays in control; the organization stops losing good work to closed tabs.
Discoverable when promoted
Teammates can read, fork, and build on promoted artifacts. Power users compound. Skeptics participate at their own pace. No forced migration, no champion burnout.
acme.habitats.ai / workstream · live view
Today · your org
Maya R. · Controller
Monthly Close Habitat
Prompt
Draft the variance commentary for Q3 close. Flag anything over 8% vs. forecast.
Habitat response
Ran the close checklist against GL. Three variances over threshold: SaaS expense +12%, headcount +9%, vendor rebates −15%. Draft commentary attached with sources.
Shared to Finance · 2h ago · 4 teammates viewed
TeamJames P. · Head of Talent
Hiring Pipeline Habitat
Prompt
Screen this week's inbound for the Staff Eng role using our rubric.
Habitat response
6 candidates matched L4+ criteria. 2 flagged for manager review. Promoted rubric v3 from Diana's stream — kept her weighting on systems design.
Private · Promote to team?
PrivateDiana C. · CFO
Executive Reporting Habitat
Prompt
Build the board slide on burn vs. plan using the Nov dataset.
Habitat response
Pulled from the warehouse. Burn is $1.2M under plan, runway extended by 3.5 months. Draft slide matches your executive voice template.
Promoted to Leadership · originated in Diana's stream
OrgInherited, not bolted on
WorkStreams live inside Habitat OS. Same VPC, same identity layer, same audit trail, same principal-led accountability. If your CISO approved Habitat OS, they've already approved WorkStreams.
Bring your Head of People. We'll walk through what a department-wide rollout looks like, including the first promoted artifacts your org would actually use.
The Habitat Library
These are the Habitats we've built and shipped. Each one is a starting point — tailored to your processes, running on your infrastructure, extended to your integrations. You don't start from scratch.
Formalize the close checklist, reconciliation rules, and approval logic into a Habitat that runs every month.
Any vendor format in, structured data out. The Habitat learns your exception patterns as it goes.
Candidate screening, scheduling, and pipeline hygiene. Stops losing candidates to your own process.
New client setup that doesn't depend on who remembers what. The Habitat carries the institutional memory.
Real-time answers against your data, not reformatted dashboards. Your executives stop waiting for slides.
Project accounting from QuickBooks to your reporting tools, with tribal cost codes formalized into machine-readable rules.
Onboarding, performance cycles, compensation changes. The workflows currently living in one person's head, formalized.
Raw data into board-ready narratives. Your executive voice, applied consistently across every deck.
OKR tracking, cross-department alignment, exec briefings that write themselves — grounded in the data your team actually uses.
And a lot more behind the scenes. If it's a repeating workflow your team cares about, it can be a Habitat.
Custom
If the thing your team does every week doesn't fit a template, we build it. The Habitat anatomy is the same; the rules are yours.
Enterprise integrations
Habitats plug into the enterprise SaaS your team already uses. Read and write with field-level auth. Respect the access controls you've already configured. Integrations expand per engagement.
Snowflake
Query your warehouse. Write back reconciled data.
Databricks
Lakehouse access with governed schemas.
Microsoft 365
Teams, Outlook, SharePoint, Excel.
Google Workspace
Gmail, Drive, Sheets, Calendar.
Salesforce
CRM read/write with field-level auth.
NetSuite
Financial systems with role-scoped access.
Workday
HR and workforce data integration.
QuickBooks
Accounting for project-based businesses.
HRIS + ATS
Greenhouse, Lever, Rippling, Gusto.
Slack
Conversational surface for any Habitat.
Don't see yours? The integration layer is extensible — any typed tool your team can describe, a Habitat can use. We've built integrations against dozens of systems; new ones are scoped into Build & Ship.
How it works
Habitat OS is delivered through a consulting engagement, not a self-serve sign-up. You pay us to understand your workflow, build your first Habitat, and operate the platform it runs on. Each phase maps to a clear contract.
We map your actual workflow — not the documented version. Every workaround, exception, and judgment call. You receive an honest roadmap with clear build-vs-buy recommendations.
We formalize your tribal knowledge and deliver your first Habitat running on Habitat OS. Principal-led build, deployed to your environment, with documentation your team can own.
Your Habitat runs in production. We operate the runtime, maintain integrations, monitor behavior, and close feedback loops. New Habitats extend the same platform.
Trust & transparency
Two things make Habitat OS defensible to a CISO: an open-core engine your security team can read, and an enterprise platform underneath that already holds the certifications most AI startups are still chasing. We didn't build that platform — Vercel did. We built on top of it on purpose.
Below is the ground truth of where Habitat OS stands today — what's shipped, what's inherited from our platform partner, and what we're still earning at the TheFocus.AI program level.
Customer VPC, dedicated cloud account, or managed single-tenant on Vercel's enterprise AI Cloud. On-prem deployments supported case-by-case. Your infrastructure team chooses the boundary.
Our managed runtime runs on Vercel's enterprise platform — SOC 2 Type 2, ISO 27001:2022, PCI DSS Level 1, HIPAA-ready (BAA available), and GDPR with DPA. You inherit those controls at the infrastructure layer on day one.
Managed deployments use dedicated VPC isolation with static egress IPs, private connectivity to your backend systems, and NAT-gateway-controlled outbound traffic. Your allowlists stay short and stable.
DDoS mitigation, managed WAF, rate limiting, Attack Challenge Mode, and IP allow/deny rules sit in front of every Habitat endpoint. Configuration changes are logged and instantly reversible.
Customer data never leaves customer-controlled storage. Model provider keys can be customer-provided or brokered. Memory, audit logs, and session data persist in storage you own.
SAML / OIDC integration with Okta, Microsoft Entra, and Google Workspace. Role-based access control scoped to Habitat and integration level. Every action is audit-logged with request-level traceability.
The Habitat engine is Umwelten — published under an OSI-compatible license at github.com/The-Focus-AI/umwelten. Your security team can read every line before deployment.
Every engagement is led by a named principal. Your escalation path goes to the person who built your Habitat, not a support tier.
Our own SOC 2 Type I audit is underway for 2026. HIPAA BAAs, ISO 27001, and sector-specific programs are evaluated case-by-case. Security posture documentation, deployment diagrams, and data-handling practices available on request under NDA.
Secured on Vercel's AI Cloud
The managed Habitat OS runtime is deployed on Vercel — our enterprise platform partner. Customers running in our managed single-tenant environment inherit Vercel's platform certifications, network isolation, and edge protection at the infrastructure layer. For customer-VPC deployments, the same runtime is delivered into your cloud boundary.
Auditable on GitHub
The Habitat primitives — persona, tools, memory, sub-agents, evals — live in our open-source project, Umwelten. Your security team can read every line, fork it, or run it themselves. Habitat OS is the enterprise distribution: hardened, integrated, supported, accountable.
Frequently Asked
Yes. Customer VPC and dedicated cloud-account deployments are standard. We provision with your infrastructure team, your IAM, and your network topology. On-prem is available for regulated workloads.
You do. Your Habitat configuration, prompts, tools, and memory are your IP. Your operational data never leaves customer-controlled storage. If you stop the engagement, you keep everything — and because the core engine is open-source, you have continuity options.
Yes. Habitat OS routes to OpenAI, Anthropic, Google, AWS Bedrock, Azure OpenAI, and on-premise open-weight models (Ollama, vLLM). Customer-provided keys are the default. We can broker if you prefer a single invoice.
Habitat OS supports per-task fallback across providers. A critical invoice-processing step can default to GPT-5, fall back to Claude, and fail gracefully to a human-in-the-loop queue if both are degraded.
We help you migrate. Because the engine is open-source, you can continue to run the Habitat yourself or with another partner — you're never stranded. Our retention rate comes from the work being good, not from lock-in.
Two answers — because there are two layers. Platform: our managed runtime is deployed on Vercel, which holds SOC 2 Type 2, ISO 27001:2022, PCI DSS Level 1, and supports HIPAA with a BAA. Those controls apply to the infrastructure your Habitat runs on. Program: TheFocus.AI's own SOC 2 Type I audit is underway for 2026. In the meantime, we provide security posture documentation, deployment-boundary diagrams, and data-handling practices to any serious evaluator under NDA. We'd rather be honest than check a box we haven't earned.
Because we didn't want to rebuild enterprise platform security from scratch while also delivering agent systems. Vercel gives us a platform with SOC 2 Type 2, ISO 27001:2022, PCI DSS, HIPAA support, Secure Compute (dedicated VPCs with static egress IPs), and a managed firewall with DDoS mitigation — already audited, already battle-tested. Our job is the Habitat runtime, the integrations, and the principal relationship. Everything below that, we inherit from a platform that's already trusted by teams with CISOs who don't accept "we're working on it."
LangChain is a framework, not a managed runtime — you're on your own for security, identity, and operations. Hyperscaler agent platforms lock you to one vendor and don't carry your cross-SaaS tribal knowledge. Copilot Studio is Microsoft-shaped and Microsoft-operated. Habitat OS is a dedicated runtime for agents that carry your team's rules across whatever tools you actually use.
The first conversation is about your workflow, your infrastructure, and your constraints — not ours. We'll tell you honestly whether Habitat OS fits.
Whether you need a quick Vibe Check or a full Habitat built on Habitat OS, we'd love to hear what you're working on.