Your systems are watched all night and fixed by morning.
Your infra person stays in charge. Ingot finds what breaks, writes the fix and waits for their OK, or merges by the rule they set.
The night checkout broke.
Example- 02:12amAn update goes live. Checkout stops working.
- 02:15amIngot notices and opens a ticket with the cause.
- 02:31amThe fix is ready. It waits for your person’s OK, or merges by the rule they set.
- 02:34amTheir rule merges it: a small change, and the tests pass.
- 02:40amCheckout works again. Ingot checks it and closes the ticket.
- 08:00amIn the morning, your person sees what happened and what waits.
What you get
You hear it from Ingot, not from customers
An outage at night reaches you in plain words, with the fix on its way.
One page every Monday
What broke, what got fixed and what waits, in words anyone can read.
A known monthly bill
One price for the company. No seats: users are free.
What your infra person keeps
Every fix is a pull request
They review it like any other change.
The two switches
Auto-fix and Auto-deploy are theirs, and off until they turn them on.
Your own API key
Past the plan’s allowance, the agents run on your key. Your person pastes it in the console.
One plan for one company.
Solo is $199 a month for one company, with two concurrent agents.
20 runner hours a month.
$50 of model usage a month on us, then your own API key.
Questions
Does Ingot replace our infra person?
No. It works for them at night and on the boring fixes. They decide what merges and what deploys.
What does it cost beyond the plan?
Model usage past the allowance, on your own API key with your provider. Nothing else, unless you ask for an add-on.
Talk to us for 20 minutes.
Bring your infra person. We’ll show what Ingot would catch on your systems.