Most developers do not want to be in the dashboard business. They want to ship features. EQQ lets the data team own “queries and data APIs” as a platform, so developers spend their cycles on the actual product.

The loop we want to eliminate

Create an API key in under a minute - zero controller, zero Swagger, zero boilerplate.
Create an API key in under a minute - zero controller, zero Swagger, zero boilerplate.
  1. PM: “I need a list of customers who did X in the last 7 days.”
  2. Dev: writes a controller, DTO, repo method, test.
  3. Code review, QA, deploy.
  4. PM: “can you also include Y?” → repeat.

The loop EQQ enables

  1. Data steward builds a query in EQQ. Parameterized.
  2. Every query is an API: POST /api/usequery/{id}/execute.
  3. PM edits the query directly; endpoint reflects immediately.

What developers keep

  • Type safety on the call site - generate a typed client from the query schema.
  • Auth - API keys, MFA, roles, all already there.
  • Observability - audit log, latency, row counts, out of the box.

When not to use EQQ as an API

Write endpoints. EQQ is query-first by design. Every call to POST /api/usequery/{id}/execute reads data; it does not insert, update, or delete rows. If your integration needs to mutate data, write that endpoint in your own service and use EQQ as the read layer for verification or audit queries alongside it.

Public internet APIs. EQQ authenticates callers via API keys passed in the X-API-Key header and is designed for trusted internal consumers. If you need a public-facing API, place a dedicated gateway service in front and let EQQ serve as the governed data source behind it, not the public endpoint itself.

Hot-path, sub-10ms APIs. EQQ executes SQL against your relational database on every request. For endpoints that must respond in single-digit milliseconds at high concurrency, keep those paths in your application service with an in-memory cache. EQQ is the right choice for operational reporting, dashboards, and integrations where a few hundred milliseconds of query latency is acceptable.

For the 80% of internal APIs where a governed read-only endpoint is the actual requirement, EQQ eliminates the boilerplate entirely.