A bigger hive. The same wall.

Not yet. We're readiness-stage. The controls SOC 2 Type II evidences (silo isolation, encryption, audit logging, deletion) are already built and enforced in the architecture. What's left is the audit itself. That means engaging an auditor and completing the observation window Type II requires, and that window hasn't opened yet.

No. An admin manages your team's seats and policy. They can see audit metadata for the team silo: who did what, when, at a category level. An admin has no path into a member's personal silo. That's true by construction, backed by the architecture, not a promise we're asking you to trust.

For enterprise tenants, we can pin a tenant's data, encryption keys and model inference to a region. That's the same silo wall and isolation, just drawn around a region instead of around you. It's a deployment we scope in the enterprise conversation, rather than a default flipped on for every account.

There's no public API live yet. What's specified is the model it will ship on: a credential scoped to a single silo. Every call routes through the same gateway and policy engine the app itself uses. That credential can never grant itself more autonomy than you've handed it.

A skill is a user-authored automation: when this happens, do that. It's a binding of triggers and actions Beemy already has, with no new execution primitive involved. A skill lives inside exactly one silo and can't reach across the wall. It can only act at the autonomy level you've already granted that surface.

Talk to us. Most enterprise requirements get worked out in that conversation directly, not through a self-serve form. That's true for custom integrations, compliance reviews and white-glove onboarding alike.