A semantic layer, no free-form SQL
Si picks metrics, dimensions, filters and periods; DataxLand builds the query from versioned definitions; Si runs no SQL of its own when answering.
Connect Jira so your IT team can ask Si about tickets, incidents and changes without writing JQL. DataxLand loads the issues, projects, statuses and change history you choose; Si proposes how to classify issue types as support tickets, incidents or deployment changes, and you approve. Si then answers about ticket volume, SLA breach rate, first response time, incidents, mean time to recovery and change failure rate.
Free plan with no time limit · No card required · Sample workspace ready in minutes
Example questions Si answers from the metrics below, once the source is connected and the model approved.
| Metric | Definition | Unit |
|---|---|---|
| IT support tickets | Number of IT support tickets (incidents and requests) opened in the period, by open date. | Count |
| SLA breach rate | Tickets breaching SLA divided by tickets opened in the period.= SLA breaches / IT support tickets | Ratio (%) |
| Average first response time (hours) | Average hours from ticket creation to first response, across all tickets opened in the period.= it_response_hours_total / IT support tickets | Number |
| Incidents | Number of incident-type tickets opened in the period, by open date. | Count |
| Mean time to resolve (MTTR, hours) | Average hours from open to resolution for incidents resolved in the period.= it_incident_hours_total / Resolved incidents | Number |
| Change failure rate | Failed changes (failed or rolled back) divided by changes deployed in the period.= Failed changes / Changes deployed | Ratio (%) |
Si picks metrics, dimensions, filters and periods; DataxLand builds the query from versioned definitions; Si runs no SQL of its own when answering.
Standard (pack metric), Approved (workspace metric checked before use), Unconfirmed (exploratory answer, clearly labelled).
In the app, Slack, Telegram, Microsoft Teams or MCP, Si uses the same read-only tools and your permissions in the workspace.
Ask inside the workspace in the language you use; Si answers in the same language, with the metric source and confidence level.
Link your account with a one-time code; ask in a private chat or a group bound to the workspace.
Create an expiring, revocable token (plans with MCP) so Claude, Cursor or your own agent call the same tools.
Choose Add source → Jira, enter your Atlassian domain, email and API token, then pick the projects to load.
Si proposes how to read issues and statuses and maps them to the pack's standard model; you fix the highlighted fields, answer the multiple-choice questions and approve the build.
Ask in the app, connect Slack or Telegram with a one-time code, or create an MCP token for Claude, Cursor or your own agent.
No. Si only reads the workspace's approved metrics; there is no tool that writes to Jira, and Si never runs SQL it wrote itself on your data when answering.
No. Personal data columns are hashed on ingest and masked before they reach Si; no dashboard, API or MCP returns the original values.
Yes, through the DataxLand MCP server with a token that expires and can be revoked. MCP tokens come with the Small Business plan and above; on Starter you ask Si in the app, Slack and Telegram.
Each person must link their DataxLand account with a one-time code and hold the Analyst role or higher, and an admin must link the group to exactly one workspace before Si answers with data.
Connect Jira →Use Si over MCP →
Free plan with no time limit · No card required · Sample workspace ready in minutes