The contract sets the mandate. The code enforces the limits. Your committee decides.
Each venture is held by three layers, and we claim nothing beyond them. Below: exactly what each one covers, what is never connected, and what we don’t have yet.
Figure 1. Three layers of three different kinds: a contract, code, and a monthly service.
The mandate
Written into the contract
- Hypothesis, market and brand: yours, or a neutral brand.
- A budget capped in the contract; nothing beyond it without your written agreement.
- Stop criteria and their date, written before launch.
- The offer and the brand validated by you before go-live.
- Confidentiality; code, content, accounts and data in your name; exit planned from the first day.
The limits
Enforced in code
- A cost ceiling and a time limit on every work cycle.
- Daily activity limits per function, and a global concurrency limit.
- One gateway per venture for deployments, DNS changes, outgoing email, payment-catalogue changes and secret reads.
- Ventures kept apart, each with its own access and credentials.
The trace, the pause, the decision
Recorded, then decided every month
- An append-only operating journal, and an audit log of every gateway call.
- Every change versioned and attributed to the function that made it.
- A pause at any time stops all activity and closes gateway access.
- Every month, at the Monthly review, your committee decides: continue, adjust, stop or accelerate.
Contract terms are engagement commitments. Code mechanisms are capabilities of the technology. The Monthly review is a service.
What the code enforces, and its exact scope.
Stated as precisely as the code allows, no further.
| Mechanism | What it does | Exact scope |
|---|---|---|
| Cost and time | Each work cycle runs under a cost ceiling and a time limit. A cycle that exceeds either is stopped and its partial work recorded. | Per work cycle. The budget cap of a venture is a contract term, read at each Monthly review. |
| Activity | Daily activity limits per function and a global concurrency limit apply, whatever the model decides. | Per function and per day; concurrency across all ventures. |
| Gateway | Deployments, DNS changes, outgoing email, payment-catalogue changes and secret reads go through one gateway scoped to the venture. Each call is written to an audit log. | Outgoing email and payment-catalogue changes are idempotent: a retry cannot send the same email twice or create a duplicate price. |
| Separation | Each venture has its own access token, secrets configuration, deployment space and domain set by a human operator, browser profile and encrypted credential vault. | Logical separation between ventures. |
| Journal | The operating journal is append-only: the database rejects any modification or deletion of a recorded event. | Enforced by the database itself, whatever the model does. |
| Business objectives | A task tied to a business objective cannot be closed without a measured result attached; only a person can cancel it. | The result is attached by the function that did the work, then read by your committee at the Monthly review. |
| Steer and pause | A written directive triggers immediate re-planning and persists across cycles. Pausing a venture stops all its activity and closes its gateway access. | At any time, by a person. |
Nothing connects to your systems.
A venture is built beside your core, not inside it. It is written into the contract.
- No connection to your information systems.
- No internal data needed.
- Orders and requests reach your teams through a channel agreed at framing.
- If you offer the venture to your customers, you do it through your own channels, with tracked links; no customer file is transferred.
What we don’t have yet, and what we exclude.
Certifications
Blaast holds no SOC 2 or ISO 27001 certification today. We answer your security questionnaire in detail.
High-risk uses
We exclude the high-risk uses defined by the EU AI Act: no hiring, credit or health ventures.
Personal data
Where we process personal data for you, a data processing agreement under GDPR Article 28 is attached to the contract, with the list of subprocessors involved. Data processing
Report a vulnerability
Write to us at hello@blaast.app, describing the issue and how to reproduce it. We take no action against research carried out in good faith.
In 30 minutes, see how an operated business is built and run.
By video, with the founding team. We look together at where a first venture could sit beside your core. Under NDA if you wish.