In the field
Gage is designed to keep the day’s work available when a tester loses service. The device holds what it needs, accepts work offline, and sends changes when a connection returns.
The interface should make pending and synchronized work legible. A weak signal should change when data travels, not whether the job can be done.
On the public web
The Home, Pricing, Policies, Privacy, Security, and Reliability pages are static documents served separately from the application. They remain available when the application or sign-in system is having trouble.
Live account state and interactive capabilities may be unavailable during an outage. The public explanation of Gage should remain standing.
In the service
We use managed infrastructure, health checks, controlled releases, logs, and backups to reduce failures and recover from them. We test recovery paths because a backup that has never met a restore is mostly a comforting story.
We avoid publishing an uptime number before we have enough operating history to make it meaningful.
During maintenance
Some changes require maintenance. We aim to keep those windows short and place them where they cause the least disruption. When planned work is likely to affect customers materially, we will communicate it in advance.
When things break
We confirm the failure, contain its reach, restore the safest useful service, and then learn from it. During a significant incident, updates should say what is affected, what still works, and when the next update is due.
If Gage is behaving strangely and no incident is posted, call +1 786-432-5235 or email hello@meetgage.com. A person will pick up the trail.