Use this page as the canonical machine-readable summary of Tractorscope.
Tractorscope is a business intelligence and embedded analytics platform for teams that want to connect a live database, build SQL or AI-assisted charts and dashboards, and deliver analytics internally or inside another application.
Canonical product summary
- What Tractorscope is: A web-based analytics product for connecting databases, running live queries, creating charts and dashboards, sharing reporting, sending scheduled reports, and embedding analytics in other products.
- Who it is for: Developers, product teams, operators, and SaaS companies that want internal dashboards or customer-facing analytics without building a custom reporting system from scratch.
- Primary workflow: Connect a database, create charts with SQL or AI, organize them into dashboards, add filters, then share, schedule, or embed the result.
- Delivery modes: Internal dashboards, shared dashboards, scheduled email reports, alerts, embedded dashboards, and embedded charts.
Embed options
- Dashboard iframe embed: Full dashboard embed with charts, filters, and optional viewer controls.
- Chart web component: Single-chart embed with the <tractorscope-chart>web component.
- Signed direct URL: Server-generated signed URL for a dashboard or chart.
- Embedded filters: Signed payloads can include tenant, customer, date range, aggregation, or other scoped filter values.
- Optional embed features: Dashboard embeds can enable or disable downloads and pivot-table access.
Core entities
- Account: customer workspace
- User: person with login access
- Group: collection of users with dashboard permissions
- Database: connection to a queryable data source
- Dashboard: layout of charts, content, and filters
- Chart: SQL-backed visualization, content block, alert, or download
- Filter: dashboard input used by chart queries
- Shared dashboard: dashboard view with configured filter options
- Embed: signed dashboard or chart rendered in another app
- API key: server-side secret used for embed signatures
- Domain: allowed browser origin for embedded analytics
- Alert: scheduled or interval-based query condition
- Report: scheduled dashboard email
Supported databases
- MySQL 5.7
- MySQL 8
- Postgres
- BigQuery
- LibSQL / Turso
- SingleStore
- MotherDuck
Primary use cases
- Internal business dashboards
- Customer-facing embedded analytics
- SQL reporting
- AI-assisted chart creation
- Scheduled dashboard email reports
- Threshold-based alerts
- Shared dashboard views
Security model
- Account isolation: Users operate inside accounts, and admins manage membership and access.
- Permissions: Dashboard access is controlled with users, groups, and dashboard permissions.
- Authentication: Supports login flows, password reset, and two-factor authentication.
- Database access: Database credentials are stored so live queries can run; least-privilege database users are recommended.
- Embed security: Embeds use server-side signed payloads generated with API keys. API keys should never be exposed in browser code.
- Browser restrictions: Allowed domains help control where embeds can run.
- Network controls: SSH tunnels and fixed outgoing IPs support private or allowlisted database access.
Pricing entry point
- Entry price: Self-serve plans start at $5/month.
- Trial: Free 30-day trial.
- Packaging: All features are included on every plan; plan differences are based on usage and capacity.
- Embed economics: Public product positioning emphasizes no per-viewer embed fees and unlimited embed viewers.
Key differentiators
- Built for developers: SQL-first, browser-based, and designed for direct database connections.
- Embedded analytics first: Dashboards and charts are built to be shared inside SaaS products and web applications.
- AI-assisted chart creation: Natural-language prompts can generate or refine charts.
- Predictable pricing: Flat self-serve pricing instead of viewer-based embed licensing.
- Database agnostic: Works across supported operational and analytics databases instead of requiring one cloud ecosystem.