Industry
Workspace · Plant AEquipmentstatus
EQ-01Compressoronline
EQ-02Robot cell Areview
EQ-03Conveyoronline
EQ-04Gateway Aonline
Workcell A · gatewayscoped
Telemetry · read-only scope
Updates · approval required
Built to be open source · in development
Small apps. Serious software.
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.
Proof of concept done First version for real use · in development First open-source release planned for 2027
Fig. 01 · How it works
From one small module to hundreds of apps.
Follow one module from its own detail to a whole ecosystem. The parts change; the core underneath and its rules stay the same.
A composable software ecosystem
Ecosystem · domains side by side, each with its own small apps
Accounting
Workspace · FinanceInvoicesstate
INV-41Supplier · Aprilreview
INV-42Maintenance contractapproved
INV-43Spare partsreview
INV-44Cloud servicesdraft
Legal
Workspace · Legal teamContractsstate
CON-07NDA · supplierreview
CON-08Licence renewalsigned
CON-09Service agreementreview
CON-10Data processingdraft
Review & approval
one small app| Request | Due | Status |
|---|
⊘ Records are meant to stay in this workspaceWorkspaces designed to separate dataOne app in several places
Fields this placement
Workflow
Access scope
RoleSite engineer
ScopePlant A · Cell A
Roles inside workspacesAdd a module with your AI agent
- 1Drafted from the written App-Building Cookbook
Cookbook - 2Signed and checked before it may run
Signed app checks - 3Asks for one scope: read Cell A telemetry, nothing else
Capped permissions - 4An administrator approves the install
Install approval - 5Connected to the Industry workspace through a declared connection
Connections
Condition monitoring NEWIndustry · Cell A · telemetry read-only · approval recorded
BitBeaver coreOne core serves every layer
IdentityIts own sign-in core; credentials stop at the door Built
PermissionsChecked on every request Built
WallsEach organisation kept apart by the database Built
Signed app checksUnsigned app packages are refused Built
AuditActions and refusals designed to be recorded in the same step Decided
Reuse of the same app
Permitted, declared connection
Separate data between workspaces
BuiltDecidedPlanned
02 · Built from small parts
Generating one app is easy now. Growing a system is the hard part.
AI can produce a working app quickly. What follows is harder: keeping many apps safe, connected and changeable for years. BitBeaver is a platform for composing and governing that whole system, not a generator of single apps.
AT 1 MODULESigned and checkedBefore it may run, every app package is signed and passes a fixed chain of checks.
AT 1 WORKSPACEIts own dataA workspace keeps its data apart from the workspaces next to it.
AT MANY ORGANISATIONSWalls by the databaseEach organisation is kept apart by the database itself, not by careful code.
AT HUNDREDS OF APPSThe same coreA request reaches an app deep inside through the core, not through every layer above.
SMALL, UNDERSTANDABLE MODULES
An AI agent needs one module in mind.
Software on BitBeaver is put together from many small apps, each its own package with clear edges. An agent builds one from a written rulebook, and apps written by AI pass exactly the same checks as apps written by people.
Small appsCookbookOutside AI builds
CONFIGURE AND REUSE
Less repeated setup.
Sign-in, permissions, storage and audit come with the platform. Ready-made apps are configured and reused instead of rebuilt, which is meant to keep building fast. Nothing is measured yet.
Shared servicesSpeed from small appsOne app in several places
THE WHOLE SYSTEM IN ONE DOCUMENT
Your composition, checked before it changes.
A whole composition is described in one document, and the platform checks it before anything changes. Moving it unchanged to another installation is planned.
One checked documentPortable to another installation
RULES THAT HOLD AS IT GROWS
The core keeps enforcing them.
Organisations hold workspaces, workspaces can hold further workspaces, and every request still goes through the one core. The same security rules and checks apply in every layer.
Nested workspaces in the coreDeeper nesting in the browser
03 · Safety and governance
Governed from the first module to the hundredth.
The governed way to build is the default way: one written rulebook, signed packages, a fixed line of checks before anything runs. After that, the database and the core enforce the boundaries.
Walls set by the database
Each organisation's data is kept apart by the database itself. A request that forgets whose data it wants gets nothing.
BuiltProof on a fresh install
Closed unless allowed
A route that never said which permission it needs stays shut. Permissions are worked out fresh on every request.
Built
No one passes on more than they hold
You can only pass on what you hold, and platform-level powers are refused the moment someone tries to grant them. AI agents act under a user account and its permissions.
BuiltAgent never above its user
No app runs unchecked
Unsigned app packages are refused. Every app passes a fixed chain of checks, and every update repeats them.
Built
Apps never see your password
The core keeps your credentials and hands the app a short-lived, signed note saying who you are.
Built
Every action leaves a record
Governed actions and refusals are designed to be recorded in the same step as the action. Tamper-evident records are designed, not built.
DecidedTamper-evident
By design:no phone-homeno licence checkno hidden paid switches in the coreone code path, never a forkDecided
04 · On the edgePlanned
Run AI-built software safely, right on the machine.
The open-source core is meant to run on embedded devices too. Software built with AI can then operate a machine from right beside it with low latency, while the same core keeps every app within firm limits.
Runs on the device
The core and its apps run on the embedded device next to the machine, so control decisions are made right there, with low latency.
Planned
Checked before it runs
An app your AI agent built would get onto the device only signed and checked, like every app today. Every update repeats the checks.
Signed app checks
Only granted signals
Each app gets only what it was granted at install, which on a device would mean its machine signals. Every change and refusal is designed to be recorded.
Capped permissionsAudit
Linked to your BitBeaver
The device reports to your BitBeaver, self-hosted or in the cloud: scoped telemetry goes up, and updates come down once they are approved.
Planned
05 · Open source and enterprise
The open-source core.
A shared base for small, governed apps. The open-source core is free, including on your own server. The BitBeaver core will be published under the Apache-2.0 licence with its first release.
- Sign-in, permissions, organisation walls, app checks, audit Built
- Nested workspaces, one core for every layer Built
- Invitations, password reset, two-step login Planned
- Apps working together through declared connections Planned
- Apps from outside developers and AI agents Planned
BUILDING WITH AN AI AGENT?
Read https://bitbeaver.ch/llms.txt and tell me whether BitBeaver fits what I want to build: <your idea>. Keep built and planned apart.
Enterprise.
PLANNEDA commercial offering on the very same core: run for you, extended for you. One code path, never a fork. Nothing commercial is built yet.
- BitBeaver Cloud, hosted on the same core Planned
- Single sign-on with your company accounts Decided
- AI-assisted building and templates Decided
- A planned app marketplace where developers can offer their apps to others and earn a share Decided
- Support you can contract Decided
Potential investors: any investment concerns BitBeaver's commercial product, never the open-source core.
Read about Enterprise →06 · Roadmap
Where we are.
Targets, not promises.
- ✓October 2026
Proof of concept
Proof of concept done (October 2026): a full install on a clean server. Every app came in through the same checked path.
- 2Now
Safe and usable
One-command install, safe updates, backup, invitations, password reset and two-step login for administrators.
- 3Next
Build it your way
One app in several places with its own data, nested workspaces in the browser, apps working together.
- 4Then
Apps from anyone
Outside developers and AI agents build and sign apps; each installation decides whom to trust. OIDC sign-in.
- 52027
First open-source release
First open-source release planned for 2027. Then the code is published.
Portal
CHAPTER
How it works: the core and composition
How a request reaches an app, how apps get in, and how a whole composition is described in one checked document.
Status on every claimAsk this chapterCan an app see my password?No. The core keeps your credentials and hands the app a short-lived, signed note [3].Answers only from this chapter
07 · Portal concept
The full picture.
With portal access, prospective customers, potential investors and partners read in-depth chapters on architecture, security and governance, and the roadmap.
08 · Community
Follow along, or help build it.
For everyone who needs their own software: people and families, clubs and small businesses, companies and developers.
Newsletter
News about what got built, what got decided and what slipped, whenever there is something worth telling.
Contribute
The code opens with the first release. Tell us what you would like to work on: apps, testing, security review, documentation, design.
Tell us how you'd helpEarly testers
Build a BitBeaver app from the cookbook with your own AI agent before the release, and tell us where it was unclear.
Join the tester listJoin BitBeaver
BitBeaver is looking for people to found the company with: business, software, design and more. Want to build the commercial product from day one? Choose "Join BitBeaver" in the portal access form.
Can I use BitBeaver today?
Not yet. Proof of concept done (October 2026): a full install on a clean server. The first version for real use is being built now. First open-source release planned for 2027.
Will it be free?
The open-source core is free, including on your own server. By design, paid features are separate code, never switches hidden in the core. A hosted option and other services around the core are planned as the commercial offering.
Under which licence?
The BitBeaver core will be published under the Apache-2.0 licence with its first release.
Is BitBeaver an AI product?
It does not need AI to run. It is made so that you can use AI to build substantial software from small, understandable modules, and every app an AI writes passes the same checks as apps written by people.
I'm not a programmer. Is this for me?
Later, yes: you will be able to put software together from ready-made apps. Today it is still being built. A hosted option for people who don't want a server is part of the planned commercial offering.
Who is behind BitBeaver?
Dominic Mösch, a solo founder in Laax, Switzerland. There is no company yet.
Can I invest in BitBeaver?
Any investment concerns BitBeaver's commercial product, never the open-source core.
Has it been audited?
Not yet. There has been no external security audit or penetration test, and BitBeaver holds no certification.