Essential
For moderate-traffic apps where continuity matters but isn't mission-critical.
What's included
- Bug and incident fixes
- Security updates
- Uptime monitoring
- Email support
SLA: response within 24h — fix within 5 business days
Going live isn't the finish line — it's the start. We keep what we built together stable, secure, and evolving, with clear commitments and service levels that match your stakes.
Why TMA
What we cover
What can't wait — incidents, bugs, vulnerabilities.
What keeps the product alive — small changes that don't warrant a project.
Service levels
Each tier matches your application's criticality and how fast you need us. SLAs are contractual.
For moderate-traffic apps where continuity matters but isn't mission-critical.
What's included
SLA: response within 24h — fix within 5 business days
For actively used production apps with regular users and real business continuity needs.
What's included
SLA: response within 8h — fix within 48h
For apps where downtime directly hits revenue or operations.
What's included
SLA: response within 2h — fix within 24h — 99.9% availability commitment
SLAs are defined in the contract with penalty clauses if we miss them. We commit to what we can sustain — not to what sounds reassuring at signing.
Handover
At the end of every Rehzzo project we formalise an application audit — code health, dependencies, watch points, documentation. That baseline feeds the TMA agreement. No surprises six months after launch.
We configure tooling for your tier — availability, performance, application errors. You get alerts. We get alerts. Often before you notice.
We define scope, SLAs, evolution allowance, and termination terms. Everything is written down — including our commitments and penalties if we fall short.
A dedicated channel, regular reporting per tier, and a planned evolution roadmap. Not something you sign and forget.
Our commitment
We wrote it. No time lost reverse-engineering an unfamiliar codebase, no regression risk from missing context.
If we miss our responsiveness commitments, the contract defines consequences. This isn't sales patter.
We don't only react to incidents. We anticipate, propose, and schedule. Your product moves forward even without a new major project.
If you bring maintenance in-house or switch providers, we plan knowledge transfer. No information hoarding — it's not in our long-term interest.
Tooling
— plus Rehzzo Cloud for hosting when it fits.
FAQ
Let's agree on the service level before go-live — not after the first incident.