Stop hiring DevOps. Your cloud gets a colleague who reports to you every morning.
Tudovu reviews your AWS account on a calendar, fixes what it finds as pull requests in your own repo, and keeps the evidence for the audit. You answer yes, no, or reviewed. Nothing changes until a person merges.
~5 minutes to connect · no card · a sample cloud and GitHub to try it on
Mapped to common compliance and security frameworks
A colleague who works to a calendar, so nobody has to remember to open a dashboard.
Snippy is the part of Tudovu that behaves like an employee. It has a calendar of standing duties, an inbox for the account's events, a case file for everything it handles, and a reporting line: a person on Slack it sends its work to and asks to sign off.
Configuration drift never gets a head start, so compliance never falls behind it.
Every message leads with the conclusion, lists only what changed, and stays under twenty lines.
A message that scrolls is a message that gets ignored, so Snippy's are short, say what they want from you in one line, and sign with how to reply.
worker-1 runs at 9% for two weeks; one size down saves $31/month · confidence high · PR ready
Assumptions: on-demand prices, us-east-1, 30-day month
Snippy: I never delete anything; every change is a pull request.- Morning briefing: what changed, what waits, what it did
- Findings watch: new critical and high since the last look
- Access review: what changed in IAM; your reply is the sign-off
- Reclaimer sweep: resources nothing manages, new since last look
- Cost briefing: spend and forecast, assumptions shown
- Drift: every stack against its template
- Rightsizing: two weeks of CloudWatch against the price list
- Cost sentinel: idle resources quietly costing money
- Custom control: a read-only report you describe in a sentence
- Outcomes: what Reclaimer delivered; the ledger credits are earned against
Your AI DevOps team: design, ship, fix, move, and prove compliance.
Each product stands on its own. A read-only AWS role is the one thing they share, and the upgrade path between them. Pick one on the left to see what it says.
The app on that one box, moved without a weekend.
You run a read-only script on the instance and answer six questions. Reclaimer generates the CloudFormation, opens a pull request, rehearses the stack idle before it serves, then moves the data with every row and every byte counted. The numbers below come from our own lab runs, and we say so on purpose.
Discover
- One read-only script on the box: image, ports, mounts, variables by name, secrets never by value
- The database beside the app, and which variables carry its connection, compared on the box
- Six intake questions no scan can answer: who, when it may stop, how people reach it
Convert and rehearse
- A deterministic CloudFormation stack, every derived value explained in the PR
- Deployed idle, rehearsed with one task and its own health check, served only on a healthy verdict
- A failed rehearsal gets a bounded fix proposal; nothing that weakens TLS or host checks gets through
Migrate and cut over
- Offline copy inside your window, counts after the freeze, files by bytes
- Cutover adds deletion protection; unfreeze is a one-file PR that starts the old box again
- Every plan is content-addressed: what you approved is what runs
Pricing you can read without booking a call.
We are in early access, so some of these are list prices and the page says so. Scans, discovery, drift and the savings estimate stay free.
- A daily allowance of Architect turns
- Snippy in Slack and the CLI
- Guardrails and deploy previews on every draft
- No card, no subscription
- 1 credit to adopt a resource or convert an app
- 3 credits for a verified data migration
- Packs: 5 for $99 · 20 for $349 · 60 for $899
- A credit is earned when the outcomes ledger records a delivered result
- Your domain, unlimited questionnaires and visitors
- Documentarian answers from your evidence
- Connecting an AWS account upgrades the same contract
Does it change anything in my account?
No. Every change is a pull request in your repository, deployed by your own workflow when a person merges. Snippy never restarts, terminates or deletes anything itself, and says so at the end of every message.
What access does it need?
A read-only role you create from a CloudFormation template we publish. Each extra ability, such as the role Reclaimer's migration workflow assumes, is a separate consent switch and a separate parameter on that stack, so you grant by privilege class, never all at once.
Where is the evidence for the audit?
In the case file for each thing Snippy did: the check, the pull request, the deploy, the check again. Documentarian answers questionnaires from that record and tells you when it cannot find a source rather than guessing.
What is not built yet?
Terraform output, a rehearsal that runs entirely inside your account, and live billing. We keep a page that separates what is proven from what is planned, and the site follows it.
Watch a morning go by in ninety seconds.
A briefing, a regressed finding, a pull request, a merge, and one application moved off its box. A ninety-second demo that plays on its own; share the link.