SSO and SCIM: scoped, not live
Beemy has no single sign-on and no SCIM provisioning today. The enterprise rollout will add them. We plan to use SAML 2.0 or OIDC with your identity provider. Then a seat will follow the person you add or remove there.
Enterprise & Platform
A bigger hive. The same wall.
For teams of 50+: the enterprise rollout will add SSO and admin controls. Compliance readiness and region residency are scoped with you. All of it rests on the isolation Beemy already enforces for one person. We state plainly what is live and what is not.
On this page
For teams of 50+
Need a bigger hive?
Teams of 50+ get custom pricing and a conversation with a person. That conversation covers what the enterprise rollout will add, such as SSO and admin controls. It also covers custom integrations, compliance reviews and onboarding. The sections below say what is live today.
Identity & administration
SSO, deprovisioning and an admin boundary: scoped, not live.
Deprovisioning: the design we build to
Deprovisioning is not live today. The enterprise rollout will build it so that offboarding someone in your identity provider revokes their access on the next check. It will leave no long-lived grant to claw back later.
The admin boundary
The design: an admin manages the hive, not a member's personal silo.
No admin console exists today. In the enterprise rollout, an admin will manage membership, seats and policy. They will read auditmetadata for the team silo: who did what, and when, by category. We design it so that an admin has no path into a member's personal-silo content. It is the same wall, drawn around your whole team.
Compliance
SOC 2 Type II readiness.
For us, most of SOC 2 Type II means naming and evidencing controls that the architecture already enforces. We are not building them from scratch. Type II is a window, not a snapshot. An auditor must watch the controls hold over time. That window has not opened yet. Beemy is readiness-stage and not yet certified.
Silo isolation
Personal, work and public knowledge live in separate stores. This is the same wall as on our Trust page.
Envelope encryption + KMS key hierarchy
Each tenant has its own encryption key. A managed key hierarchy wraps it. No single shared secret protects everyone.
Immutable, hash-chained audit log
Beemy adds every sensitive action to a hash-chained log. Nobody can edit or delete an entry after the fact. The log only grows.
Crypto-shred deletion
A person on our side runs an account delete. It destroys the encryption keys that protect the account. The data then cannot be recovered. One audit record stays on purpose.
No-train model routing
Beemy routes inference requests so that your content never trains shared models. This is the same commitment as our Trust page, enforced at the routing layer.
TLS 1.3 everywhere
Traffic between you and Beemy uses TLS 1.3. So does traffic between Beemy's own services.
An always-on security CI gate
Every change passes automated security checks before it reaches production. The gate runs on every commit.
The controls above run today. The audit is still ahead of us. We must engage an auditor and complete the observation window that Type II needs. The full commitments are on our Trust & Security page. You can also read the honest version of "enterprise-ready".
Procurement usually asks about accessibility too. TheAccessibility page lists what we test and what is still short.
Data residency
EU and regional residency, for enterprise tenants.
Beemy is built to pin a tenant's data, encryption keys and model inference in one region. It uses the same silo wall and row-level isolation that separate personal from work, drawn around a region instead of around you. We scope it in the enterprise conversation. It is not a default for every account today.
Talk to us about your region →For builders
Build on Beemy: the model we build to.
A scoped API
No public API is live yet. This is the design we build to. A credential covers a single silo and can open a context for that silo only. Every call runs through the same gateway and policy engine as the app. A write waits for your approval until you raise the dial on that surface. A credential cannot give itself more autonomy than you gave it.
Skills & custom workflows
Skills are not live yet. This is the design we build to. A skill will join triggers Beemy already watches to actions it already takes. It will add no new way to run code. A skill will live inside one silo and will not reach across the wall. It will act only at the autonomy level you already gave that surface. Writing a skill will never give it more power than you have.
Questions
Questions we hear.
Are you SOC 2 Type II certified?
Not yet. We are readiness-stage. We have already built the controls that SOC 2 Type II checks: silo isolation, encryption, audit logging and deletion. The audit itself is still ahead. We must engage an auditor and complete the observation window that Type II needs. That window has not opened yet.
Can an admin read my personal inbox?
No admin console exists today, so no admin can read anything through Beemy. The enterprise rollout will add one. We are designing it so that an admin manages seats and policy and sees audit metadata only: who did what, and when, by category. The design gives an admin no path into a member's personal silo.
Is my data stored in the EU today?
For enterprise tenants, we can pin a tenant's data, encryption keys and model inference to a region. This is the same silo wall, drawn around a region instead of around you. We scope it in the enterprise conversation. It is not a default for every account.
Can I build on Beemy's API today?
No public API is live yet. We have specified the model it will ship on. A credential covers a single silo. Every call goes through the same gateway and policy engine as the app. A credential cannot give itself more autonomy than you gave it.
What's a "skill" and can it act across my silos?
A skill is an automation you write: when this happens, do that. It joins triggers and actions that Beemy already has. It adds no new way to run code. Skills are not live yet. When they ship, a skill will live inside one silo and will not reach across the wall. It will act only at the autonomy level you already gave that surface.
We need something specific: custom integrations, a compliance review, dedicated onboarding. Now what?
Talk to us. We work out most enterprise needs in that conversation, not through a self-serve form. This covers custom integrations, compliance reviews and hands-on onboarding.
Read next
Get your time back.
Beemy is in private beta. We send invites in rolling batches. We cannot promise a date. When your invite arrives, connect Gmail. Beemy sorts your inbox in that first session.
You're in
You're in the hive. You get no email now. We write to you once, when your invite is ready.
While you waitLast updated