Operating status.
Eight written commitments, measured monthly. This page is the public ledger — what we promise, how we measure it, what happens when we miss.
This is not a real-time dashboard.
Some vendors publish a status.example.com page with colour-coded uptime bars driven by a synthetic monitor. Most of those bars say "operational" when the customer's site is broken, because the monitor checks an unrelated endpoint.
We do not publish that page. What we publish here is the eight written covenants of the Dwize Care Year, the way each is measured, and the path of consequences when one is missed. Real-time uptime telemetry per customer site lives inside the operator's monthly status email — not on a marketing page.
Eight commitments. Each measured.
Same-price renewal
Renewal at the same product tier costs exactly Year 1 price. No annual hike, ever.
- Measure
- Renewal invoice = Year 1 invoice
- Threshold
- 100%
- If missed
- Refund of any difference, immediately
Two-day update
Any in-scope content update is live within 2 business days of receipt.
- Measure
- Receipt timestamp → live timestamp
- Threshold
- ≤ 2 business days
- If missed
- Operator acknowledges miss in writing; no automatic credit (rare event)
Two-hour acknowledgement
Every inquiry is acknowledged within 2 business hours during business days.
- Measure
- Inbound timestamp → first reply timestamp
- Threshold
- ≤ 2 business hours
- If missed
- Acknowledged in writing; tracked monthly
Named operator
Every Care Year has one assigned human at Dwize. Their WhatsApp is in the contract.
- Measure
- Operator name in signed contract appendix
- Threshold
- One named human
- If missed
- Re-assignment with 7 days notice; never silent
Monthly check-in
Even when the buyer is silent, Dwize reaches out at least once per month.
- Measure
- Outbound check-in count per Care Year per month
- Threshold
- ≥ 1
- If missed
- Tracked; consistent miss escalates to operator review
99.95% uptime
Measured monthly. If we miss in any month, a credit goes to the next renewal.
- Measure
- External uptime monitor (operator-disclosed source)
- Threshold
- ≥ 99.95%
- If missed
- Credit applied to next renewal, automatically
Honest 30-day out
Pro-rata refund within first 30 days if not satisfied. Clean offboard.
- Measure
- Refund request received → refund processed
- Threshold
- ≤ 7 business days
- If missed
- No questions, no friction; offboard handover provided
No-lock-in handover
Code, content, domain, native binaries — yours at year-end if not renewing.
- Measure
- Handover artifacts shipped before expiry
- Threshold
- 100% before Day 365
- If missed
- 30 days additional read-only hosting if delivery delayed
Where Dwize runs.
Static surfaces (Site, marketing) on Cloudflare Pages global edge. Commerce surfaces (Store, Brand) on a multi-tenant React backbone with Razorpay-native checkout. Every customer's data is in a schema-isolated tenant they own.
Cloudflare global network
Sub-second loads from any Indian PoP. Same edge that powers Discord, Shopify, Canva.
Cloudflare Pages prerendered HTML/CSS/JS
No PHP runtime, no edge database, no plugin ecosystem. Static is the strongest security posture.
Multi-tenant React commerce (Store / Brand)
Schema-isolated per customer. Razorpay-native UPI / cards / netbanking + COD.
Buyer-owned domain, Cloudflare DNS
Your domain. Your DNS. We hold neither in a way you cannot leave.
iOS + Android compiled per platform
Distributed via App Store + Play Store. Buyer owns the developer accounts.
Razorpay (India) · Stripe / PayPal optional
Indian rails first. International rails as bolt-on for the small fraction of orders that need them.
The incident path is in writing too.
- 01
Detect
External uptime monitor flags a miss; operator is paged within 5 minutes during business hours.
- 02
Acknowledge
Operator confirms receipt to buyer over WhatsApp / email within the standard 2-hour window — even if outside business hours, on a best-effort basis.
- 03
Restore
Restoration to last-known-good state. Median time to restore for static surfaces is <15 minutes (CDN cache repop). For commerce surfaces, <60 minutes (tenant rollback).
- 04
Postmortem in writing
Within 7 days of resolution, the operator sends a written postmortem: what failed, what fixed it, what changed to prevent recurrence. No fluff, no marketing language.
- 05
Credit if covenant 06 missed
If the monthly uptime drops below 99.95%, a credit is automatically applied to the next renewal invoice. No buyer action required to claim it.
Status pages are vendor language. Contracts are buyer language.
What you actually buy is the contract. The status of any given month lives in the operator's monthly status email, not in marketing colour-bars.