The pitch for AI agents usually goes like this: describe your idea, go make a coffee, come back to a finished product. Then you come back to a confident paragraph, a broken demo and no idea what actually changed. Protaura is my attempt to build the less exciting, more useful version. A founder describes what to build, a small team of AI teammates does the work, and nothing is published without the founder's approval. It's in beta.
The problem with agent demos
Solo founders don't lack ideas. They lack hands. The promise of AI agents is extra hands, but most tools stop at narration: the agent tells you what it would do, or what it thinks it did, and you're left checking its homework with no trail to follow.
I wanted the opposite. Work that leaves evidence. Changes you can review as real changes, not as a demo. And a hard rule that the human stays in charge of what goes out.
The team
| Teammate area | What it covers |
|---|---|
| Vision | What you're building and why |
| Project scope | What's in the first version and what isn't |
| Design and brand | How it looks and feels |
| Infrastructure and code | Making it real and running |
Office and Mission Control
Work is split between the Office and Mission Control. The Office is where the teammates and their work live. Mission Control is where you see what's happening across a mission and where decisions wait for you.
Everything is recorded in an audit trail. When something changed, you can see what changed and who on the team changed it. That sounds like bureaucracy until the first time you need to know why a file looks different from yesterday.
A mission from idea to approved change
How work moves through Protaura.
- You describe what you want to build.
- The AI teammates split it into vision, scope, design and code work.
- They do the work and record it in the audit trail.
- Changes stop at an approval gate.
- You review the real change, not a demo of it.
- Only approved work is published.
An agent that tells you it succeeded is not evidence. A change you can open and reject is.
— the principle behind the approval gates
Approval gates are not friction
People sometimes ask whether approval gates slow things down. They do, a little, the same way code review slows things down. The alternative is finding out what your agents did after it's live, which is slower in every way that matters.
The gates also change how the agents' work gets shaped. If every change has to survive a human looking at it, the work has to be presented as something reviewable: a concrete change with context, not a wall of narration. That's a better product for the founder and, honestly, a better discipline for the software.
Plans, in general terms
The free plan runs the full mission and agent loop, not a crippled preview. You bring your own API keys, and you can import issues from GitHub so the team starts from work you've already written down. Paid tiers raise caps and add governance features. Current prices are on the site; I'd rather link than repeat numbers that may change.
Bring your own keys. Bring-your-own API keys on the free plan means you control the model account and its costs. It also means the free plan is genuinely usable, rather than a demo that runs out after a few clicks.
What's honestly still beta
Protaura is in beta and the portfolio lists it as active development. The agent loop works, but AI teammates are still AI: they'll misread scope, make design choices you don't like and write code that needs review. The approval gates aren't decoration. They're there because the work needs them.
I'm also not going to claim Protaura replaces a team. It's a way for one person to get more done with a clear record of what was done. That's a smaller claim, and I can actually stand behind it.
Before you hand work to any AI agent team
- Make sure every change stops at an approval gate
- Check there's an audit trail you can actually read
- Review real changes and not summaries
- Keep control of your own API keys
- Start from written issues instead of a vague prompt
Note: Who it's for. Solo founders and small teams who want to move faster without giving up the final say. If you want a hands-off magic button, this isn't it, on purpose.
Take a look
Protaura is at protaura.com. The rest of my projects live on spicanet.net/products.
Originally published on spicanet.dev.
Top comments (0)