This dashboard keeps your snapshots, settings and encrypted API keys in a free Upstash Redis database attached to the Vercel project. Nothing else is required.
Open the project in Vercel → Storage tab → Create Database.
Pick Upstash → Redis (the free plan is plenty) → Continue.
Connect it to this project for all environments. Vercel adds the KV_REST_API_URL / KV_REST_API_TOKEN variables itself.
Redeploy (Deployments → ⋯ → Redeploy) so the functions pick the variables up, then come back here.
Step 3 of 3 · optional
Lock it down.
Two secrets were generated for you and are stored in your database. Moving them into Vercel as environment variables keeps the encryption secret out of the same store as the encrypted keys and signs the daily refresh. Optional — everything works either way.
Redeploy, then click the button below — the copies in the database are removed once they match.
Setup & security
This dashboard.
Pending secrets
Generated on first load and still stored in the database. Paste them into Vercel to harden.
Diagnostics
Copies a small JSON — template version, setup state, storage, account count, the last refresh's steps and warnings, missing MCP tools. Never keys, passwords or emails. Paste it into a problem report.
Deletes every account, snapshot, setting and the password from the database. The Vercel project and your HYROS accounts are untouched; the dashboard returns to first-load setup.
—
0 = account default · last click only
Only leads/sales in these stages count; spend stays. Pick none for the standard report.
Applies on the next Refresh.
Drag table headers to reorder columns.
app.hyros.com · performance report
app.hyros.com · crm
Attribution note.firstSource / lastSource are populated
by the MCP only for leads that arrived via a tracked click. Leads created by the
Stripe and HubSpot integrations have no click history, so their source is genuinely
empty — not a reporting bug. Income is joined from hyros_get_sales
by email, because the lead object carries no revenue field.
