Count FAQs

Start by setting context at the right level: workspace for organization-wide rules, project for team-specific logic, so agents give consistent, checkable answers before you open things up more broadly. Test any new rule in a canvas first and refine it until the agent responds the way you want, then promote it up.

For business users, start with a limited audience and expand as you see the agent's answers hold up consistently over time. Data users can move faster than this, since they're able to check the agent's queries and workings directly rather than relying on trust alone.

Combined with project-level permissions and telemetry, teams can self-serve with confidence, and you can see exactly how it's being used as adoption grows.

Yes. Every workspace has telemetry giving you an always-on view of agent activity: who's been where, what's been queried, and what your agents have been doing on your behalf. This sits alongside Count's permissions and project structure, so you always know not just who can access what, but what's actually happening day to day.

Yes. Count is built to be interoperable, so the trusted context and analysis you build in Count works wherever your team already does. Connect through Count's MCP server to use Count from agentic tools like Claude or Cursor, call the public API to run analyses or sync context from your own workflows, or bring Count's agent directly into Slack. Wherever the question gets asked, the answer stays consistent.

Yes, and yes. Most of an agent's analysis runs on Count's own fast in-memory engine, DuckDB, rather than your data warehouse, cutting warehouse costs from agents by up to 80%. Your warehouse is still there when you need its full power, but the bulk of day-to-day querying doesn't have to touch it.

Yes. Count Metrics is an open, version-controlled semantic layer for pinning down definitions precisely: business metrics, complex SQL, and repetitive joins, defined once and reused everywhere. Agents build directly on top of it at runtime, so the same trusted definitions show up in every analysis rather than being reinvented each time.

Yes. Count is SOC 2 and GDPR compliant on every plan, with HIPAA compliance, SSO, SCIM provisioning, and data residency options available on Enterprise. Within a workspace, a project-based permission hierarchy lets you scope data and context to the right people and agents, and telemetry gives you an always-on view of what's actually happening. You can read more in our trust report and security overview.

Count connects to your data wherever it lives:

Warehouses and databases (live or snapshot):

Internal tools: CRM records, support tickets, shared drives, and anything else reachable via MCP.

Files:

The web: let the agent search for public data and context when it needs it.

Other:

Yes. You can query multiple databases and CSV files in the same canvas. You can also use Python and SQL together and reference results from one in the other, so a SQL cell can build on a Python cell and vice versa.

Check out our pricing page for all the pricing details.

When you join Count you'll have a free 2-week trial in which you can access all the features and have unlimited users and canvases.

If you want to extend your trial or chat, send us a note at hello@count.co

You can see a wide range of canvas examples and templates on the Gallery section of our website. We also regularly showcase how companies are using Count in Company Spotlights and webinars on our blog.

Yes, we have a growing Slack community of fellow Count users. You can join us here.

Last updated: 03/08/26