Nobody sees it.
This is the actual product, not a diagram. Jana describes a process, Claude Code builds it, the tests gate the deploy, and nothing reaches production without a frozen, audited version.
Supplier invoices arrive in the shared mailbox. Match each one to its purchase order by supplier, amount and date. Post matched invoices to the accounting system.
Anything over 50 000 CZK, or anything that doesn't match, goes to Jana for approval before it's posted. Keep a record of who approved what.
backend/match.py, backend/approve.py, frontend/app… 31 tests from the sample file.api.csob.cz isn't an approved host yet, so posting is stubbed until IT allows it in the firewall.| ID | Result | Description |
|---|---|---|
| R-01 | pass | Every invoice is matched to exactly one purchase order, or flagged. |
| R-02 | pass | Matched invoices are posted to accounting with the PO number. |
| R-03 | fail | Invoices over 50 000 CZK are held for approval before posting. |
| R-04 | fail | An approval records who approved, and when. |
| R-05 | pass | Duplicate invoice numbers are rejected. |
| … | 26 more | all passing |
Publishes jana-novakova into the main code area, then builds and deploys every container in this business process to dev. Your changes below become the new main once the deploy succeeds.
| api.csob.cz | allow | approved by it.admin · 09:40 · staging + production |
| api.ares.gov.cz | allow | approved by it.admin · 2 Sep |
| smtp.company.cz | allow | approved by it.admin · 2 Sep |
| api.openai.com | deny | requested by matcher · not approved |
| cdn.somevendor.io | deny | requested by frontend · not approved |
| 0.0.0.0/0 | deny | default · staging + production |
What IT sees. Every screen above is visible to the admin: the description, the agent's chat, the tests, the diff, and the history of who promoted and signed what.
What the agent can't see. Production. It works in dev with its own database, file store and network. Promotion to staging and production is a human decision, recorded.
The left column is what's happening in most companies right now. The right is the same people, with the same AI tools, working inside a Bailey.
Automations built with Claude, dashboards in Lovable, none of it visible to you.
Your people use the same agents in a place IT can see and control.
visible to ITDid the agent delete the production database again? Nobody meant it to reach production.
The agent works in dev. Production only takes a frozen, audited version.
agent · no route to prodYou don't know what the code does, what it connects to, or where it sends data.
Default-deny egress, sealed secrets, isolated stages — on every app, built in.
firewallsecretsisolationNo record of who did what, or where the data went.
Append-only history for NIS2, DORA, ISO 27001, SOC 2 and GDPR.
append-only logDuplicate tools, no owner, no idea which one is the real one.
Employees open approved apps from one place. Admins decide what's approved.
one owner eachEach one is a button in the product, and each one leaves a record.
Moves a version from dev to staging. All tests must pass first; the deploy button won't let you otherwise.
Locks the exact version on staging. Nothing can change under the auditor's feet.
An independent auditor reads the frozen version and signs it. The count shows what's done.
Promotion to production stays locked until the version is frozen and the audit is signed.
One press back. Production returns to the previous signed version.
A separate stage with its own backups, so a bad day costs you a rollback, not your data.
A Bailey is the line between your people's ideas and your production systems. Everything crosses it on the record.
The runtime enforces them on every app. The evidence writes itself into the append-only history.
Access control, logging and supply-chain evidence come from the runtime, not from a policy document.
Every change is frozen, tested and signed before production, with the record to show for it.
The technical controls an Annex A review asks for are enforced, and the enforcement is logged.
Change management and logical access are evidenced by a history nobody can edit.
The Article 30 register and Article 28 processor agreements build themselves as external hosts are approved.
“We went from piecemeal scripts and manual copying to a cohesive, governed platform that handles our core telecom and financial workflows. BitSwan keeps us agile without compromising our security audits.”
Thirty minutes. We show you Bailey, you tell us about your work, and we find out whether there is something here for you.
Demo available in English or CzechThirty minutes. Leave us your number and we'll call you to arrange a time.
We'll call you on that number to arrange a time for the demo.