What happens to your system after we leave.
Our whole pitch is that we hand you the keys. A pitch like that is worth exactly as much as what it says about the day after, and about the day we stop existing. So here it is in writing, on a page with a date on it.
Six promises. Every one of them is checkable in your own repository, which is the point — a commitment you cannot verify is marketing.
Your system does not depend on us
It runs on your accounts, in your cloud, under your credentials. There is no Alot Labs service anywhere in the request path, no API of ours it calls, no dashboard of ours it reports to. If this firm shut down between two of your deploys, nothing you run would notice.
The license outlives the engagement
Anything of ours that ends up inside your system arrives under a license that survives the engagement at no ongoing cost. It does not lapse, it does not come up for renewal, and we cannot revoke it. Everything built on top of it is yours outright, from the first commit, in your repository.
No kill switch, no beacon, no expiry
We do not write license checks, usage telemetry, phone-home calls or expiry dates into anything we hand over. You do not have to take that on trust: it is your source code, and grep is free. If you ever find one, it is a defect and we will remove it.
Handover is a deliverable with a date, not a goodbye email
Source, architecture documentation, a runbook, and working sessions with the team who will own the thing. The test we hold ourselves to is not that the system runs. It is that your engineers can change it without calling us. If they cannot, the engagement is not finished, whatever the schedule says.
If Alot Labs winds down, we say so and we publish
A notice goes on this page, and an email goes to every client we have handed a system to. Any internal tooling your system genuinely depends on is released under a permissive license, along with the runbooks. Nothing you rely on becomes orphaned because we stopped operating. A firm that promises to hand you the keys has to mean it in the case where the firm is gone.
We will tell you when not to build it
If a query and a rule solve your problem, that is the recommendation, and we will help you write the rule. This costs us engagements and we keep doing it, because the alternative is a firm whose advice you have to discount for its incentives.
What this is not
It is not a warranty, and it is not a support contract — a retainer is a separate arrangement and you can cancel it monthly. It is not a promise about uptime we do not control, or about a model provider’s pricing, or about what happens to code after your team has changed it. It is a promise about our conduct, which is the only thing here we actually own.
If this text ever changes, the change is logged here with its date. A standing commitment that can be edited quietly is not one.