What it is
Vesqo is a web application. It connects to the tools a SaaS company already runs, read-only, every fifteen minutes, and keeps a history of each: revenue (Stripe and the like), product analytics (PostHog), engineering (GitHub), errors (Sentry), support (Crisp, Intercom), the CRM (HubSpot, Attio) and news about the companies that pay you. Customers are joined across those sources into one account each, with what they pay.
Twice an hour, and the minute a release ships, a set of rules reads the sources against each other and against the same hours the week before. When they disagree, Vesqo writes a signal: what changed, the release it dates to, the customers in it, the money, and the next step. A critical one reaches the team at once, by email, Slack or webhook; the rest go into one email at seven, ranked, with the money next to each line. Questions about the data are answered from the same record, and automations open the issue or post the write-up where the team works.
The signals are written by rules, not by a model: the same numbers give the same signal, every time, and each says what it read. Claude (Anthropic) answers the questions asked of Ask Vesqo and sorts news headlines by topic; it does not decide what is a signal.
Who it is for
A founder or a small team running a SaaS product, or several, with paying customers and a stack of four to ten tools that do not know about each other. The team that would rebuild the story after an incident by hand, in five tabs, and would rather not. Companies whose customers are companies get the most from it, because a Stripe customer, a Sentry user, a support contact and a CRM deal can be joined by their email domain.
It is not for a company with a data team and a warehouse, which can build all of this, and not for a company with a customer success team and a platform for it. Vesqo is for the team that will not have either for a while.
What it is not
- Not a replacement for Sentry, PostHog, Stripe or any tool it reads. It reads them; the trace, the funnel and the invoice stay where they are. Vesqo vs Sentry, Vesqo vs PostHog.
- Not a dashboard builder. There are charts, but the product is the write-up.
- Not a chatbot over your database. Ask Vesqo is the last step, after the signal; it answers with what it read.
- Not a CRM, a help desk or a billing tool. It writes to a source only through an automation you made.
How it is built
One application and its database, at Hetzner Online GmbH in the European Economic Area (Falkenstein, Germany), with encrypted nightly backups that stay in the EU. Every connection is an API key with read scope or an OAuth grant with the least it can ask for, encrypted at rest and deleted the minute a source is disconnected. Every workspace's data is isolated at the database level, and everything done or read in a workspace, by you or by us, is in its audit log. Security and data says the rest.
Who runs it
Vesqo is operated by Carlos Soares (MotionKeys), Rua de Santo Antonio 654, Penafiel Porto, tax id PT260967114. For accounts, workspace settings and billing Vesqo is the data controller; for the customer data a workspace's tools send, the workspace is the controller and Vesqo its processor under the terms. Write to hello@vesqo.app; privacy questions and rights requests go to privacy@vesqo.app.
The name
Vesqo is one word, said as it is written, at vesqo.app. When you mention it, the short form that fits is “Vesqo, business observability for SaaS”. The mark is the three dots at the top of this page; icon.png is the square one. For an AI agent that would rather read one page than crawl, the site is also at llms.txt.
