TripDeck Admin
Usage, cost and account reporting for TripDeck.
Usage, cost and account reporting for TripDeck.
Usage and cost at a glance.
Total trips saved, and the average trips and requests per user.
Whether anything is about to cost money this month.
The monthly bill, spend over time, and API calls by provider.
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.
Sign-ups, retention, what people plan, and how much they share.
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.
Speed, reliability and infrastructure usage.
These describe the infrastructure, not the product. Where a metric has a published target, it shows what counts as good.
How fast the app feels to real visitors.
Visitors per day over the selected range.
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.
Projects the monthly bill for a given number of users. It covers costs only, not revenue or growth.
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.
Feature switches, announcements, provider routing, alerts and maintenance.
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.
What is stored for venues, flights and rate limits, with controls to clear it.
Addresses that hit a request limit and are being slowed down. Reset one to remove its limit.
What has happened recently: sign-ins, recovery attempts, blocked addresses, and provider failures.
Who can sign in to this admin panel, and which sections they can use.
Grant or revoke who can sign into this admin panel, and which sections they can use. Requires the User Manager permission to edit.
Search activity, guide health and release notes.
What people type into the Help Center search. For searches that return nothing, add or update existing guides.
Checks every help guide is reachable, indexed, and tagged well enough to be found.
Write the "What's new" page in the Help Center. Each day is one release: add a note on a day that already has one and the new bullets join it.
How to read the reports, manage access and troubleshoot problems.
Access to this admin panel is protected by your account credentials:
Admin permissions are additive, ranging from baseline read-only reporting (Level 1) to full administrative control (Level 4):
| Tier | Accessible Views | Capabilities | Required Flags |
|---|---|---|---|
| Level 1: Read-Only (Lowest) | Summary, Cost & Usage, User Behavior, Site Health, Cost Simulator, Help Center | View all traffic charts, operational metrics, third-party bills, and system health reports. Cannot change settings, feature toggles, or user accounts. | is_admin |
| Level 2: System Controls | All Level 1 views + System Controls | Turn features on or off, post announcement banners, switch flight providers, and clear stored caches. | is_admin + can_system_controls |
| Level 3: User Manager | All Level 1 views + User Manager | Look up registered users, make someone an admin, assign permissions, log users out, or delete accounts. | is_admin + can_user_manager |
| Level 4: Super Admin (Highest) | All views and tabs | Complete, unrestricted operational control and user management across the entire admin panel. | All flags enabled, or sign in via ADMIN_PASSWORD |
The quick overview screen. Shows total accounts, total trips planned, guest vs signed-in usage, and this month's estimated third-party API bill.
Breaks down every call to outside providers like Google Places, HERE, Mapbox, and flight tracking. Shows costs, error rates, and lets you download a CSV.
Shows how people use TripDeck. Daily, weekly, and monthly active users, trip creation frequency, how often trips are shared, and device types (phones vs laptops).
Monitors page load speeds, Cloudflare edge traffic, response error rates, and database storage capacity.
An interactive planning tool. Move the sliders to see what our monthly bills will look like as more people start using TripDeck.
Shows what people type into the Help Center search bar. Searches that return 0 results tell us which help articles we need to write next. Also lets you write the What's new page.
TripDeck logs third-party resource usage to calculate and forecast costs:
If an outside service is having an outage or charging too much, you can turn off that specific feature instantly under System Controls > Feature switches without any downtime or code changes:
Post a message across the top of TripDeck under System Controls > Announcements to alert travelers to updates or planned maintenance:
TripDeck can switch between two providers under System Controls > Provider routing:
If outdated data gets stuck or to free up database storage, use the tools in System Controls > Cache & database:
Receive automatic operational notifications when outside service quotas approach monthly limits or when error rates spike, configured in System Controls > Alerts:
Every change made to settings, feature switches, banners, or user roles is automatically recorded in the Activity log with a timestamp and the admin who made the change.
The User Manager tab lists every registered passkey account. You can type an ID into the search bar to locate an account quickly. For each user, you can see:
You can change permissions directly using the switches in the table:
If an account authenticator is compromised or an account needs to be removed, you can log them out immediately to invalidate their session, or delete the account record permanently.
What you might see: Error alerts in Cost & Usage, or reports that flight lookups are timing out.
What you might see: High cost alert in Summary, or sudden surge in calls on Cost & Usage for Google Places or Mapbox.
What you might see: You lost your phone or laptop with your passkey, or biometric sign-in is failing.
What you might see: You need to run an urgent database migration or server fix.
What you might see: A traveler or office network reports HTTP 429 "Too Many Requests" errors when opening trips or searching places.
What you might see: Weather forecast badges or currency conversion rates appear frozen or out of sync with external sources.
What you might see: High database storage indicator in Site Health, or write failures when travelers save trips.
What you might see: Slack or Discord channels stop receiving quota warnings or provider failure notifications.
What you might see: A user contacts support because they replaced their phone or lost access to their biometric authenticator.
What you might see: Travelers report that links pasted into notes boards (Instagram, Yelp, Airbnb, or news articles) display only the raw URL without a title or image thumbnail.
What you might see: An administrator leaves the team or loses a laptop, requiring immediate administrative access termination.
What you might see: Error rate badge in Site Health turns red with an elevated percentage of 5xx HTTP responses.
What you might see: Collaborators editing a trip offline report seeing a duplicate trip marked as a conflict copy.
What you might see: Support receives repetitive questions about a new feature or policy.