Reliability and continuity
RentalTide is the system of record for your bookings, payments, and operations. We design it so a single bad day — at AWS, at your dock, or at our office — does not turn into a bad week for your business. This page covers the broad strokes of what we do to keep the platform running and what your team can do when something does go wrong.
For deeper technical detail (regions, services, recovery time objectives), see the technical appendix.
What we protect against
| Scenario | What it looks like | Who keeps you running |
|---|---|---|
| A single AWS data centre failing | Brief pause while traffic moves to the other zone; up to about 15 minutes if it is the database's zone | AWS multi-AZ infrastructure, automatic |
| An entire AWS region going down (us-east-1) | Admin and online booking unavailable until AWS restores the region; status page kept current | AWS recovery; RentalTide on-call keeps you informed |
| Your local internet drops | Booking widget and admin are unreachable from your dock | You — offline procedures below |
| Our servers crash or a deploy goes bad | Errors on specific pages; automatic restart and rollback, usually within minutes | RentalTide on-call + automated health checks |
| Fire, flood, or physical loss at your location | Your devices may be gone; your data and bookings are untouched | Cloud-hosted data, just sign in from any device |
| Fire, flood, or physical loss at our office | No impact — we have no on-premise servers | Cloud-hosted everything |
Where your data lives
RentalTide runs entirely on Amazon Web Services, not in our office. That means:
- A RentalTide laptop being lost, stolen, or destroyed has no effect on the service or on your bookings, customers, or payments.
- A fire or flood at your location has no effect on your data. Sign in from a phone, a hotel laptop, or a tablet and you are back online.
- We do not need to ship hardware to recover from any disaster.
Your primary database runs in AWS's us-east-1 region in Northern Virginia, with its storage replicated across three independent data centres (called Availability Zones). Continuous backups are taken automatically, and we can restore the database to any moment in the last thirty-five days. Backups are kept in the same region; we do not currently keep a copy in a second region. Identity images for Australian locations are stored in AWS's Sydney region.
What happens if AWS has a bad day
AWS designs each region to tolerate the loss of one data centre with no customer impact. We rely on that. In the rare cases where an entire region has degraded service:
- Detection — automated monitors alert RentalTide on-call within minutes.
- Communication — we update the status page at
status.rentaltide.comand post in your support channel. - Recovery — RentalTide does not run a standby region today, so during a regional outage we wait for AWS to restore service in
us-east-1, then confirm everything is healthy before we call it resolved. The web app and booking widget pages keep loading from the CDN, but anything that needs live data waits for the region.
While we recover, your team can still do a lot — see the offline procedures below.
What happens if your internet drops
This is the most common outage you will actually experience. RentalTide is a web app, and if the dock has no internet, neither does the booking widget or the admin panel. Here is what to do.
Take walk-ups on paper
Keep a printed walk-up sheet on the counter with these fields:
- Customer first name, last name, phone, email
- Asset type and quantity
- Start time and intended return time
- Signature line for liability waiver
- Payment method (cash, card terminal direct, "bill me later")
Photos of the driver's licence and signed waiver work fine on a phone. Enter them in RentalTide once internet is restored.
Keep your card reader running
Your Stripe terminal can complete payments without RentalTide as long as it has cellular or hotspot connectivity. The transaction will still settle correctly. Reconcile it against the paper sheets when you re-sync.
Use a hotspot
A phone with cellular service is enough to get the admin panel back up on one device. Use the Today's Hub view on that device as your single source of truth until the dock connection returns.
Don't worry about the booking widget
Customers trying to book online during your local outage just see a normal "site unreachable" message from their browser. They will retry. We do not lose their attempts — our analytics show the booking widget itself remains available globally even when individual locations are offline.
What happens if our servers crash
Servers fail. Bad deploys ship. We plan for both:
- Automatic restart. If a server process crashes, our container orchestrator restarts it within seconds and shifts traffic to healthy instances.
- Health checks. The load balancer checks every server every 10 seconds. A server that fails three checks in a row is taken out of rotation automatically.
- Bad deploy rollback. New servers must pass their health checks before they take traffic, and the old ones keep serving until they do. If the new version keeps failing, the deploy rolls back to the previous version automatically.
- Status page. Major incidents are posted at
status.rentaltide.comwith regular updates until resolution.
If you see errors that persist for more than a few minutes, reach out in your support channel. We will already be on it, but it helps us confirm scope.
What happens if there's a fire, flood, or worse
The honest answer: your data and bookings are unaffected. Everything that matters is in the cloud, replicated across three data centres. There is no scenario short of a regional AWS catastrophe where you lose customer records, payment history, or future bookings.
If your location is unsafe to operate
- Sign in to RentalTide from any device anywhere in the world.
- Mark affected dates as closed under Operations > Calendar > Block dates.
- Use the bulk messaging tools to email or text every customer with a booking in the affected window.
- Use the cart recovery tools to follow up once you reopen.
If you lose physical hardware (terminals, printers, tablets)
- Your data is fine.
- A new tablet or laptop with a browser is all you need to be operational again.
- Stripe will reissue terminals on request. Reach out and we will help you place the order.
If we lose office access
We have no on-premise servers, no local databases, and no critical infrastructure at our office. Engineering and support work from laptops that can be replaced overnight. The platform runs entirely on AWS and would not notice.
Offline procedures for staff
A quick reference your staff can use the moment internet drops, before they have a chance to read this whole page.
| Activity | Offline alternative |
|---|---|
| New walk-up rental | Paper sheet + driver's licence photo. Enter when back online. |
| Existing booking arrives | Mark on a printed daily list. Check them in on screen later. |
| Take a payment | Use the Stripe terminal directly (cellular or hotspot). |
| Look up a customer | Have a phone on a cellular hotspot for one device. |
| Sign a waiver | Paper liability waiver, scan or photograph for upload later. |
| Manage assets on the lake | Communicate by radio or phone; reconcile in the manifest when back up. |
| Reservations on the phone | Take notes, promise a confirmation email once you re-sync. |
Print this table and laminate it. We have a printable PDF version on request.
How we communicate during incidents
You will hear from us in three places during a real incident:
- Status page —
status.rentaltide.comis updated within minutes of detection. This is the source of truth for current status, what is affected, and ETA. - Support channel — your dedicated support channel (Slack or email) gets a message within the same window with anything specific to your location.
- Post-incident review — for incidents with significant customer impact we write a post-incident review. Ask in your support channel for the summary.
If you ever cannot reach us through your usual channel during an outage, the support email at support@rentaltide.com is monitored from outside our normal infrastructure.
Recovery time and recovery point at a glance
These are engineering targets, not guarantees, described in detail in the technical appendix. Contractual commitments are in the Service Level Agreement.
| Failure mode | Recovery time objective (RTO) | Recovery point objective (RPO) |
|---|---|---|
| Application instance crash | About 1 minute | Zero data loss |
| Bad deploy | Minutes (automatic rollback) | Zero data loss |
| Single Availability Zone failure | Minutes; up to about 15 if it is the database's | Zero data loss |
| Catastrophic data corruption (rare) | Several hours | About 5 minutes |
| Full AWS region outage | Until AWS restores the region (no standby region) | Depends on the region's storage |
Practising your own continuity plan
Reliability on our side is half the picture. We recommend every location:
- Keep paper walk-up sheets and waivers on hand for the season.
- Keep one staff phone with a cellular plan dedicated to RentalTide access during dock-wifi outages.
- Identify a backup person who can sign in and run the admin panel if the manager is unavailable.
- Test your Stripe terminal on cellular at least once per season.
- Know where to find your support channel and the status page.
If you would like help drafting a continuity plan specific to your location, reach out in your support channel and we will work through it with you.

