Contact sales
Semantic layer Platform Features Security Compare Integrations Embed FAQ Contact sales
Semantic-first AI Native Enterprise BI platform

Strixa

One business definition. Every chart, report, and answer stays aligned.

Define dimensions, measures, joins, and RLS once. Dashboards, multi-page reports, exports, embeds, alerts, and governed AI all resolve through the same published model.

Contact sales See how it works
  • Semantic layer
  • ETL & connectors
  • Query engine
  • Dashboards
  • Multi-page reports
  • AI Analyst
  • Alerts & anomalies
  • Integration rules
  • JWT embeds
  • Row-level security
  • Scheduled exports
  • Workspaces
  • Multi-tenant RBAC

AI analyst, dashboard, and report surfaces · auto-advancing carousel

Semantic layer

One definition between raw data and every answer

Ingest from warehouses and pipelines into Strixa. Configure dimensions, measures, joins, and RLS. Reuse those contracts across dashboards, reports, exports, embeds, alerts, and AI, so Revenue means one expression everywhere.

Semantic core

Revenue model Published
Revenue$4.28M
Orders18.4k

How it works

From raw tables to automated intelligence in five moves

A single governed path: connect sources, publish a semantic model, design surfaces, distribute securely, then automate with alerts.

  1. 01

    Connect and ingest

    Attach warehouses and SaaS sources. Run ETL with full, incremental, and CDC-oriented refresh where configured.

  2. 02

    Model the business

    Declare dimensions, measures, and joins so revenue means the same thing on every surface.

  3. 03

    Design experiences

    Compose dashboards and multi-page reports that consume the same semantic contracts.

  4. 04

    Distribute and embed

    Share, JWT-embed into portals, export PDF, and schedule subscriptions under tenant RLS.

  5. 05

    Monitor and automate

    Alert on thresholds and anomalies. Fire Slack, email, or webhooks when conditions match.

Distribution

Put governed, automated analytics in front of every team

Publish once from the semantic model, then reach stakeholders through the channels they already use.

  • Share links Workspace links for colleagues with RBAC-aware access
  • Embeds JWT-secured iframes for portals, with optional customer_id RLS
  • PDF and Excel Viewer exports that run queries under the same tenant and RLS rules
  • Subscriptions One-time or recurring email with scheduled PDF delivery
  • Alerts Threshold and anomaly rules with Slack, email, or webhook delivery

Platform

Everything between your database and your decision-makers

From ingestion to automated actions, Strixa is structured as production services with strict tenant boundaries, so you can grow usage without growing risk.

Semantic layer

Dimensions, measures, and relationships defined once. Generated SQL respects model scope so metrics stay aligned across dashboards, reports, alerts, and AI answers.

ETL pipelines and connectors

Connect databases and SaaS sources. Run incremental loads and CDC-oriented pipelines where configured, plus scheduled refreshes. Shape tables for analytics without leaving the platform.

Query engine

Execute governed queries against semantic models with caching and clear error paths, whether the request comes from a dashboard tile, a report data element, or an API client.

Alerts and anomaly detection

Set threshold rules or statistical anomaly detection (z-score, IQR rolling baselines) on any widget metric. Alerts fire on schedule, on view, or on refresh, with full audit trails.

Integration rules

Chain AND conditions across KPI thresholds, dataset row counts, and alert states. Trigger in-app notifications, email, webhook, or Slack, with encrypted secrets and dead-letter queues.

AI-assisted exploration

Ask in natural language against the same metrics users see in the UI. Answers stay grounded in approved model fields, not ad hoc spreadsheet logic or invented aggregates.

The problem with point solutions

One platform replaces six separate tools

Most analytics stacks are held together with export scripts and hope. Strixa is engineered as a single governed system, so your metrics stay consistent from ingestion to AI answer.

See how Strixa compares to each tool

  • 20+ Chart and viz types Bar, line, pie, scatter, heatmap, treemap, funnel, and more
  • 5 Steps to intelligence Connect, model, design, distribute, automate in one platform
  • 1 Semantic layer Metrics defined once: same logic in dashboards, reports, alerts, and AI
  • 0 Cross-tenant leaks Tenant isolation enforced at every query, service, and embed token

Security

Built like infrastructure, not a spreadsheet add-on

Every persistence path is tenant-scoped in the data model. Authentication context, not URL parameters, drives which rows, workspaces, and embed origins a session can touch.

Isolation by default

Tenant identifiers travel on the token. Services enforce them in repositories, queries, and alert evaluations.

Encrypted secrets

Integration rule webhook URLs, Slack tokens, and signing secrets are encrypted at rest and never logged.

Embed origin control

Tenant-configured allowlists restrict which domains can host embedded dashboards, enforced at the gateway.

Auditable services

Fastify microservices, typed validation, OpenAPI endpoints, and per-alert audit logs for every state change.

  • JWT
  • tenant_id
  • RBAC
  • RLS
  • Gateway
  • Repository filters
  • allowlist
  • secrets
  • audit trails

Embed overview

Integrations

Warehouse connections with real drivers

Official vendor marks for sources Strixa can extract against today.

PostgreSQL PostgreSQLSupported
MySQL MySQLSupported
MariaDB MariaDBSupported
Microsoft SQL Server SQL ServerSupported
Amazon Redshift RedshiftSupported
Snowflake SnowflakeExtract
Google BigQuery BigQueryQualified
Amazon S3 Amazon S3Partial

Full connector directory

FAQ

Straight answers

Why lead with the semantic layer?

Dashboards, reports, explore, embeds, and governed AI all resolve fields through the same published model. That is how Strixa keeps metric definitions consistent.

Is live / DirectQuery generally available?

No. Extract-based models are the primary path. Live query exists as an ops-gated pilot for selected engines.

Can I embed dashboards in my product?

Yes. Mint a short-lived JWT for a published dashboard via POST /embed/token. Use the iframe viewer or JS, React, and Angular packages, with optional customer_id RLS.

How does ETL refresh work?

Pipelines support full and incremental loads. CDC-oriented modes are available where a source and deployment are configured for them. They are not positioned as always-on streaming for every connector.

Is there public pricing?

Not on this site. Contact sales for evaluation and deployment options.

Build on governed metrics from day one

Talk through your sources, semantic models, dashboards, and embedding requirements.

Contact sales View integrations