Production readiness
Software is now built faster than it is made dependable. Production readiness is for a product that works in a demo or for a handful of users, often built quickly with AI tools, and now has to hold up for paying customers. We review it end to end, fix what stands between it and a launch, and leave a written account of every change.
What it covers.
Sign-in and access
Sessions, password or link flows, roles and permissions checked against the ways they usually fail.
Payments end to end
Checkout, webhooks, cancellations and failed payments tested against real events, so the ledger and the product agree.
Data and recovery
Backups configured and a restore actually performed, with the steps written down for the next time.
Errors and alerts
Error tracking, uptime checks and alerts that reach a person, tuned so they are worth reading.
Security review
Secrets, dependencies, input handling, rate limits and access between customers, with findings ranked by risk.
Delivery
A deployment pipeline with previews and one-step rollback, so a bad release is a minor event.
How it runs.
Audit
Two days reading the code and the running system. You get written findings ranked by risk, and a fixed price to address them.
Fixes
Changes land as reviewed pull requests in your repository, each one explained, with tests where they matter.
Launch check
We walk the product as a customer would: sign up, pay, use it, cancel, recover. Anything that fails is fixed before handover.
Handover
A report of what changed and why, a runbook for incidents, and a call to go through both.
Is it a fit.
A good fit
A web product with working core features and real users, or a launch date. Teams who built fast, with or without AI tools, and now need it to hold.
Not a fit
Products whose core features don't work yet; that is product engineering. Native mobile applications.
Questions.
Most of our code was written by an AI tool. Is that a problem?
No. It is now the usual case. We read it like any other code, and the report notes where generated code tends to hide problems so your team can watch for them.
Do we have to move to Dianthan?
No. We work on whatever you run. If the platform would remove work, we say so in the report and you decide.
Can we see where we stand first?
Yes. The free production check at dianthan.com/check looks at what's visible from outside in a few seconds. The review covers what it can't see: the code, the data and the payments.
What if the audit finds more than fits in two weeks?
The findings are ranked. You choose what is fixed now, and the rest stays in the report with enough detail for anyone to pick it up.
Other engagements.
Product engineering
Web applications, APIs and internal tools, designed and built with your team, in milestones you can use as they land.
Milestones from $5,000AI integration
Bringing models into a product so that they are dependable and their cost is understood: retrieval, tool use, evaluation, and a cost on every call.
Milestones from $5,000Operations and care
Monitoring, upkeep and incident response for systems we have built or reviewed, with a fixed allowance for small changes each month.
From $400 a month
Tell us what you're building.
A few lines about the product and what stands in the way. An engineer replies within two working days.