HeyMetra About HeyMetra
HeyMetra is a no-code AI data agent. You connect the accounts your business already runs on, ask questions the way you would ask a colleague, and get answers built from your live numbers. When a change would help, it proposes one and waits for you.
Why it works this way
A dashboard answers the questions someone anticipated when they built it. Every real question you have now is one nobody anticipated then — which is why the honest workflow ends up being an export, a pivot table and an afternoon. HeyMetra exists to close that gap: ask the question you actually have, against the accounts you actually run, and get the number with its provenance attached.
The harder half is what happens next. An agent that can read your data is useful; an agent that can change it is either the point or a liability, depending entirely on what stands between the model and your account. We put an approval gate there, deliberately and boringly, and published the limits it enforces.
How we handle your accounts
Your data stays where it lives
HeyMetra does not copy your accounts into a warehouse of ours. When you ask a question, it reads from the connected account at that moment and answers. There is no nightly sync to fall behind, no second copy of your business to secure, and nothing to re-import when a definition changes upstream.
Every answer shows its work
An answer arrives with the account it came from, the date range it used and the figures behind it. That is the difference between reporting and guessing: a fluent paragraph with no provenance is not an answer you can take to a decision.
Reading and changing are different permissions
Asking about your spend and changing your spend are separate authorisations, not one connection with a setting. Connect an account read-only and the agent can answer questions about it and never touch it — regardless of what anyone types into the chat.
Nothing changes until you approve it
When a change would help, the agent proposes the exact edit and waits. What you approve is recorded as a payload, and that payload is what runs — the model does not get a second turn to decide after you click approve. Approvals expire after 30 minutes, because the numbers they were based on go stale.
Credentials we cannot read
Where a provider supports OAuth you sign in on their site, so your password never reaches us. Access tokens and any API key you paste in are stored encrypted, never displayed back to you and never written to logs. Revoking access on the provider’s side cuts the connection immediately, with no step required from us.
We say who else touches your data
The Privacy Policy names every sub-processor — including the model providers we route through, who are contractually barred from training on your data — rather than describing them as “trusted partners”. Your data is not used to train a model, ours or anyone else’s.
The enforced numbers behind the approval gate — how much one action can move a budget, how many campaigns it can touch, how many writes a workspace gets in a day — are on the security page.
Where we are
HeyMetra is pre-launch. The product runs, integrations are being switched on one at a time, and the only way in today is the waitlist. We would rather tell you which connector is not ready than have you discover it after signing up — so every integration says plainly whether it works today or is still coming.