TripDeck Admin
Usage, cost and account reporting for TripDeck.
Usage, cost and account reporting for TripDeck.
How much travel planning TripDeck is actually holding.
Whether anything is about to cost money this month.
What this month has cost so far, and how many API requests produced it.
Spend over time, and how close each provider is to the point where it starts charging us.
What our usage would have cost without any free allowances. Useful for the shape of the trend, not the bill — the meters below show what we actually owe.
How much of each provider's free monthly allowance we have used. This is the one that predicts a real bill.
Title and image fetches for links pasted into trip notes — free/uncapped, so the question here is health, not budget.
Every provider call in the window, broken down by who made it.
Per actor, over the trailing window. “Value if unsubsidized” is what these calls would have cost without the free monthly allowances.
How many people have signed up, and how much they have planned.
How many of those people come back, and how often.
How often a trip leaves an account and reaches somebody else.
Which kinds of travel lookup people actually use when planning a trip.
Which kinds of lookup people ran over the last 30 days. Automatic weather refreshes are excluded — nobody asked for those.
Where visitors come from, what they arrive on, and which pages they land on.
Where visitors come from, what they browse on, and which pages they arrive at.
How well protected accounts are against losing access to their own trips.
Every account on TripDeck, when it was created, and when it was last used.
How fast the app feels to real visitors.
How many people visited.
How much traffic is answered from our own store instead of a paid provider. This is what keeps the bill near zero.
Today’s database usage against the daily free allowance. Engineering metric.
Set the numbers you want to model. Nothing here changes the live app.
What the monthly bill would be under the assumptions above.
Which outside services drive that projected bill, and where each one starts charging.
Estimated volume, free allowance, and any overage for each service.
| Service & Provider | Gross Requests | Calls to provider | Free Allowance | Billing Model / Threshold | Monthly Cost | Status |
|---|
If we charged for TripDeck, how many paying users would it take to cover the bill above?
The points where growth would force a paid plan.
Turn parts of TripDeck on or off for everyone.
Show a banner for outages, maintenance, or news.
Choose which outside service we ask first, and which one covers for it if that service goes down.
Get a message via webhook when a provider is close to its limit or starts failing.
Checks that each outside service is reachable and how quickly it answers.
Stored data and cache controls.
Addresses that have hit a request limit and are being slowed down. Reset to remove the limit.
What has happened recently: sign-ins, recovery attempts, blocked addresses, and provider failures.
Grant or revoke who can sign into this admin panel, and which sections they can use. Requires the User Manager permission to edit.
What people type into the Help Center search, and which searches came back with nothing — those are the guides we are missing.
Checks every help guide is reachable, indexed, and tagged well enough to be found.
Write and publish the update notes people see in the app and in the Help Center.