Overview
Self-Service Analytics with Control for Data Analysts and Freedom for Business Users
Every report is only as good as the chain behind it. OWOX draws the chain — collect, store, define once, deliver everywhere — and keeps every link governed by your data team. Hover a card to see what it touches.
01 · Connectivity
Connect data sources to an ontology model tailored to your business. Ensure data trust with automatic quality validation.
No per-connector bill. No semantic layer tax.
02 · Enablement
Get zero-hallucination answers in your AI, spreadsheets and dashboards. One governed source of truth for everyone in organization.
Powered by patented technology
03 · Ecosystem
Your data has more value when any product can unlock it. Create plugins for any customization you could imagine.
Trusted data and governed credentials without the headache
OWOX Data Marts consists of six core entities, seamlessly integrated to address the most challenging data questions you may have
Sources
Collect from the tools you already run
Ads, e-commerce, CRM and product data land in your warehouse as first-class inputs — scheduled, transparent and reproducible.
Why OWOX
- Open-source connectors. Every connector is Node.js you can read, fork and fix. No black-box ETL and no per-row pricing.
- Your warehouse, not ours. Data never sits in a vendor's cloud on the way in. It goes straight to the storage you own.
- Custom source in a day. The connector template is the whole contract — a new API is a folder, not a support ticket.
Storages
Keep it in the warehouse you already trust
OWOX runs on top of your storage. Nothing is copied out to be modelled; every data mart is a query your warehouse executes.
Why OWOX
- No second copy of your data. BI tools and semantic layers ingest and cache. OWOX reads in place, so there is one truth and one bill.
- Any warehouse, same product. BigQuery, Snowflake, Athena, Databricks, Redshift — one project can hold several, and a mart moves with its storage.
- Shared on your terms. A storage is shared for use or for maintenance separately, so analysts build on it without holding its keys.
Data Marts
Define every metric once
A data mart is the governed layer between raw tables and every report: one definition per metric, reused by every team, tool and agent.
Why OWOX
- Governance without a six-month project. Govern at the mart level — enough structure to trust the numbers, shipped in days, not a semantic-layer programme.
- Joinable, not siloed. Marts relate to each other, so ad spend meets orders without anyone rebuilding the join in a spreadsheet.
- Quality and freshness on the card. Every mart carries its last-updated time and its data-quality checks. A broken link is visible before anyone asks.
Destinations
Deliver where the question is asked
One mart powers many outputs without duplication — a spreadsheet, a workbook, a dashboard, an AI assistant that answers from governed definitions, or your own code through the API.
Why OWOX
- AI without hallucinated metrics. Claude and ChatGPT read the mart, not the raw tables. The answer uses your definition of revenue, every time.
- Spreadsheets stay live. Google Sheets and Excel refresh on a schedule from the same mart. No exports, no stale tabs.
- Every route is visible. Which report writes where, when it last ran and whether it succeeded — on the card, not in a log.
Reports
Reports that refresh themselves
A report is a saved question against a data mart: which columns, which filters, where it lands and when. OWOX runs it on schedule and writes the answer into the sheet or workbook your team already opens.
Why OWOX
- Built on the mart, not the raw tables. Every report inherits the mart's definitions, so two teams asking the same question get the same number.
- Scheduled, not exported. Triggers refresh a report on your cadence. Nobody copies a CSV on Monday morning.
- Run history on the card. Last run, status and owner sit beside each report. A failed refresh is visible before the meeting it feeds.
Plugins
Extend OWOX with plugins
Plugins read your project through the OWOX API and add the views and workflows your team needs — without waiting on a roadmap.
Why OWOX
- Built on the public API. A plugin sees exactly what the API exposes, under the same permissions as the person using it.
- Install, don't integrate. Plugins run inside OWOX. No extra login and no data copied to another vendor.
- Yours to build. The plugin SDK is open. A custom view for your team is a small project, not a feature request.