Production verification
Post-deploy smoke checks cover public health, API health, billing page render, and the live smoke sequence.
Reliability notes
Monthly reliability notes for how Luota is operated.
Luota is built around operating records, so reliability evidence needs to be public enough to inspect and boring enough to repeat. These notes summarize what is checked, what changed, what is still manual, and what improves next.
Field notes
Short essays for real workflow failure modes.
Stripe webhook outcome monitoring
A focused product page for proving billing state, entitlement, and customer access after Stripe sends a successful webhook.
Read note
A Stripe webhook returning 200 is not proof the customer got access
A focused note on why provider delivery is not the finish line, what customer-visible billing state to prove instead, and how to drill the missing-access failure path.
Read note
May 2026 evidence
What is checked this month.
Backup verification
Production database backup and freshness verification are scripted under pnpm ops:backup and pnpm ops:verify-backup.
Restore drill
Restore drill is scripted under pnpm ops:restore-drill for throwaway local verification after material data-model changes.
Security disclosure
security.txt and the vulnerability disclosure page are published with a dedicated security contact.
Marketing reliability
Public proof, accessibility, legal, security, pricing, docs, examples, status, and changelog routes are in the sitemap.
Known risk
Public reliability notes are currently manually written. The next step is to pull the deploy and backup evidence from the same ops data used internally.
May 2026
Production checks are scripted
Deploy verification, backup freshness, restore drills, Lighthouse budgets, marketing pageview checks, and disclosure updates are committed scripts instead of one-off terminal memory.
Incidents
No public customer-impacting incident is recorded here
When an incident occurs, the note will include impact, detection, timeline, root cause, resolution, prevention, and the Luota evidence that helped or should have helped.
Next improvement
Turn notes into a monthly evidence rollup
The next reliability pass should generate a private draft from deployment checks, backup verification, Lighthouse results, and the incident table before publication.
Need a concrete migration or monitoring pattern? Start with the docs, then adapt the payload to the evidence your operator needs.
Open integration docs