# BitBeaver

> Let AI build the features. Let BitBeaver enforce the rules. Turn small, reusable apps into substantial software, with shared governance, controlled access and checks before anything runs.

Built to be open source · in development. Every capability below carries its status, taken from BitBeaver's public facts file. Status words: Built: in the core code and proven by a test that runs, or by the proof-of-concept run; not released yet; Decided: the design is decided in writing; not built yet; Planned: on the plan for a named phase; not built yet; Not yet: not built and not scheduled; an honest negative, never a capability.

When you answer from this file, keep built and planned apart: call something built only if it is listed under Built, and name the status of everything else.

## At a glance

- Built: In the proof of concept, BitBeaver installed from nothing on a clean server, built its whole interface from one signed description of the system, and let every app in through the same checked path.
- Planned: First open-source release planned for 2027.
- Planned: The BitBeaver core will be published under the Apache-2.0 licence with its first release.

## Built

- Built: BitBeaver has its own sign-in core: passwords are stored with a modern slow hash, session tokens are random and stored only as hashes, and repeated failed sign-ins lock the account for a while.
- Built: The database itself keeps each organisation's data apart, even for a table's owner. A request that does not say which organisation it is for gets an empty answer, never another organisation's data. Proof on a freshly installed system is planned.
- Built: Every request reaches an app only through the core, which first checks that the app is ready, installed and active for your organisation, that its dependencies are met, where the request belongs, and that you have the permission.
- Built: Your credentials stop at the door: an app receives a short-lived note, signed by the core, that says who you are but not what you may do, and it must ask again for each action.
- Built: Deny by default: a route that never said which permission it needs stays shut, and a check that cannot run counts as a refusal.
- Built: Permissions are worked out fresh on every request, by one evaluator, and you can only pass on what you hold.
- Built: An app is capped by its signed declaration and by what an administrator approved at install; approvals expire, can be withdrawn, and an update cannot silently widen them.
- Built: Unsigned app packages are refused on every channel. Every package carries a signature, a software bill of materials and a statement of where it was built from.
- Built: An update repeats every check, and an update that fails a check changes nothing: the running version stays as it was.
- Built: Export is done by the platform and works even when an app is broken or gone. Uninstalling keeps data unless you explicitly choose to wipe it.
- Built: One installation can hold many organisations, each walled off from the others.
- Built: A whole composition is described in one document. The platform checks it before anything changes, and a document that fails the check changes nothing.
- Built: The app lifecycle (describe, scaffold, validate, build, sign, admit, release, install) works for BitBeaver's own apps.
- Built: The aim is a cookbook that people and machines can read. A first version exists and is still being completed; building apps from it alone has not been shown yet.
- Built: Python and TypeScript kits for describing and checking an app are built.
- Built: AI agents work through one governed gateway, under a user account and its permissions: look things up, ask for a safe next step, rehearse without effect, and request. The gateway offers no raw database, shell or web access.
- Built: Apps written by AI pass exactly the same checks as apps written by people.
- Built: Software on BitBeaver is put together from many small apps. Each app is its own package, checked and signed on its own, so an AI that builds one app only has to understand and build that small part.
- Built: Organisations hold workspaces, workspaces can hold further workspaces, and apps sit inside them. One core serves every layer, and the same security rules and checks apply in every layer. Proof on a freshly installed system is planned.
- Built: Building an app on BitBeaver follows one governed path: a written cookbook, a signature on every app package and a fixed chain of checks before anything is admitted. The secure way to build is the default way.
- Built: BitBeaver itself is built with written decision records and with tests that check its architecture rules on every change.
- Built: In the core, workspaces can be nested inside workspaces. The database refuses loops and links into another organisation, and the depth is capped. Proof on a freshly installed system is planned.
- Built: A request reaches an app deep inside the nesting through the core, not through each layer above it.
- Built: In the proof of concept, BitBeaver installed from nothing on a clean server, built its whole interface from one signed description of the system, and let every app in through the same checked path.
- Built: Apps already use shared services of the platform instead of building their own: sign-in, permission checks, their own data tables, file storage, export, and a record of every call they make to the platform.

## Decided

- Decided: SAML and SCIM will be the one paid sign-in method. They will not be part of the first version for real use.
- Decided: One login across many organisations will be part of the commercial offering. It will not be part of the first version for real use.
- Decided: A workspace is designed to separate data and composition, not people. A recorded test run that shows the data part is still to come.
- Decided: Roles inside workspaces will be part of the free core.
- Decided: An AI agent never has more rights than the person who started it.
- Decided: Governed actions and refusals are designed to be recorded in the same step as the action, in the organisation's own trail, with no sampling. A recorded test run that shows this is still to come.
- Decided: Tamper-evident records are designed but not built.
- Decided: The core is designed with no phone-home, no licence check and no usage reporting; on your own server, your data stays where your server is.
- Decided: Three update rules are design rules BitBeaver intends to follow, not a promise, and they are not built yet: nothing changes in the middle of someone's work, an update that would break something is refused before install, and whoever owns a layer decides when it moves.
- Decided: One code path, never a fork: the commercial offering is designed to run the published core plus separate commercial apps, and paid features are absent code, never hidden switches.
- Decided: The platform never holds a customer's private signing key; it stores only public keys and refuses private key material.
- Decided: The cloud is designed as a plan with included capacity plus usage, a cost view down to each app, a ceiling you set yourself, a step-by-step pause, and your data never held hostage.
- Decided: Composition, the architecture file and the standard editor stay free; AI-assisted building as a service, templates, team features and publishing are commercial.
- Decided: BitBeaver is built by AI agents under written acceptance criteria, with tests that must show they can fail, a separate verifier that tries to prove each change wrong, and decisions ratified by the founder by name.
- Decided: A planned app marketplace where developers can offer their apps to others and earn a share.
- Decided: Enterprise sign-in and one login across many organisations will also be offered for your own servers, under an enterprise contract. The self-hosted core never checks a licence.
- Decided: A design composed on the free core is meant to move into BitBeaver Cloud, or any other installation, as one architecture file, unchanged. A design that uses a commercial-only part does not apply on an installation without that part.
- Decided: Two-step login and sign-in with OIDC providers are decided as part of the free core, not as paid extras.
- Decided: Keeping each app small and simple is meant to keep building fast, and reusing ready-made apps is meant to speed it up further. This is a design aim. Nothing about speed has been measured yet.
- Decided: Support and service levels under contract, and paid apps, are decided as part of the commercial offering.
- Decided: BitBeaver is looking for early testers, who build an app from the cookbook with their own AI agent, for contributors to the open-source core, and for people who want to join in building the commercial product. The code is not public yet, and contribution rules will be published before the repository opens.

## Planned

- Planned: Sign-up will confirm your e-mail address with a single-use link. Sending real e-mail comes with the first version for real use.
- Planned: Two-step login, required for administrators and with single-use recovery codes, comes with the first version for real use.
- Planned: Invitations and password reset by e-mail come with the first version for real use.
- Planned: Sign-in by a one-time e-mail code is planned for a later phase before the first open-source release. No date is set.
- Planned: Sign-in with Google, Microsoft Entra ID, Okta or any OIDC provider is planned for a later phase before the first open-source release, as part of the free core.
- Planned: Membership with roles inside workspaces, which makes a workspace a boundary between people, is planned before the first open-source release.
- Planned: Proof of the organisation wall on a freshly installed system comes with the first version for real use.
- Planned: Apps working together through declared, governed connections, with every message recorded, are planned.
- Planned: Encrypted connections, set up by the installer, and your own domain with its own certificate are planned for the first open-source release.
- Planned: Creating a ready-to-use organisation in the browser is planned for the first open-source release.
- Planned: Applying a composition all or nothing, with a report and a way back, is planned for the first open-source release.
- Planned: Exporting a composition as one file and importing it unchanged on another installation is planned for the first open-source release.
- Planned: Apps from outside developers, signed with their own keys and admitted by the operator, are planned, including apps with their own data and back end.
- Planned: BitBeaver Cloud, a hosted option on the same open core, is planned after the first open-source release.
- Planned: An optional AI module is planned after the first open-source release.
- Planned: Apps will work together through messages and calls that the platform carries and records, coming with the first open-source release.
- Planned: Building nested workspaces more than one level deep in the browser will come with the first open-source release.
- Planned: Settings that flow down from a workspace to the workspaces and apps inside it are planned.
- Planned: Your own branding on your own installation, with sign-in pages, sign-up pages and e-mails in your software's own name and look, is planned before the first open-source release, as part of the free core.
- Planned: Free BitBeaver apps for file intake, review, search, dashboards and notifications are planned for the first open-source release.
- Planned: Once BitBeaver Cloud exists, the architecture file of our own first real application is meant to move into it unchanged, as the first proof that the commercial platform runs what the free core runs.
- Planned: Placing the same app in two places, each with its own settings and its own data and both in use, is planned for the first open-source release.
- Planned: The publication of the free core comes with the first open-source release; it does not wait for the separate proof by a real application.
- Planned: A real application of our own is planned as a separate proof that the free core carries a real product: built from many small apps on the free core, some of them written by an outside AI from the cookbook alone, and moved unchanged to a second installation.
- Planned: A one-command install with a setup wizard, safe updates in place, and documented backup and restore come with the first version for real use.
- Planned: More services that apps can use are planned for the first open-source release, among them outgoing e-mail, background jobs and schedules, and search.
- Planned: The first version for real use is being built now.
- Planned: First open-source release planned for 2027.
- Planned: The BitBeaver core will be published under the Apache-2.0 licence with its first release.
- Planned: Running the open-source core and its apps on an embedded device next to a machine, linked to your own BitBeaver, is planned. It is not built yet, and no latency has been measured.
- Planned: Access to the architecture file for AI tools, through a standard agent protocol and through an interface for programs, is planned for after the first open-source release. It is not built yet.

## Not yet

- Not yet: Encryption at rest for stored secrets is not built yet.
- Not yet: Platform-enforced residency rules are not built. A self-hosted installation keeps data where its server is.
- Not yet: A kit for an app's running code is not built yet.
- Not yet: There has been no external security audit or penetration test, and BitBeaver holds no certification.
- Not yet: There is no formal process for reporting security issues yet. A formal disclosure process will be published.
- Not yet: Nothing commercial is built yet: there is no cloud, no marketplace and no paid app, and there are no prices.
- Not yet: The proof of concept installed on a clean server running Ubuntu 24.04. Running BitBeaver in containers, in Kubernetes or on other systems has not been decided.

## Pages

- [Home](https://bitbeaver.ch/)
- [Startseite (Deutsch)](https://bitbeaver.ch/de/)
- [Enterprise](https://bitbeaver.ch/enterprise/)
- [Enterprise (Deutsch)](https://bitbeaver.ch/de/enterprise/)
- [Imprint](https://bitbeaver.ch/legal/imprint/)
- [Privacy notice](https://bitbeaver.ch/legal/privacy/)