What is Strata?
Strata is an AI-powered enterprise intelligence platform that turns natural-language questions into live queries, charts, exports, and dashboards across your databases, files, and email.
The product in one paragraph
Strata is built by Kronisys Inc. You sign in with your Microsoft work account, optionally connect extensions (SQL Server, OneDrive, Outlook, SharePoint, Microsoft Teams, Web search, Jira, Confluence, plus a marketplace of additional connectors), and then talk to the AI in plain English. Once your organization has connected its Azure AI Foundry, Strata works as a general-purpose AI assistant even with no extensions connected. With extensions connected, it executes SQL against your databases, searches your OneDrive, drafts and sends Outlook email, produces styled Excel workbooks and PDF reports, and builds interactive dashboards — all from a chat conversation.
The extension model
Strata grows with what you connect.
| Extension | What it adds |
|---|---|
| SQL Server | Live database queries, schema discovery, multi-connection management |
| OneDrive | File search and reading, saving AI-generated exports, folder management |
| Outlook | Email search and reading, drafting and sending email, calendar, tasks, and contacts |
| SharePoint | Access to SharePoint sites and document libraries; also powers the Knowledge Base |
| Microsoft Teams | Talking to Strata from a Teams chat, creating meetings with Teams links |
| Web search | Real-time web search for current events, prices, and documentation |
| Jira | Search and read Jira Software issues and Jira Service Management requests; create issues, comment (always as internal notes on service requests), change an issue's status and edit its fields where the organization allows it |
| Confluence | Search and read Confluence pages and list spaces; create pages and comment where the organization allows it |
SQL Server, OneDrive, and Outlook are connected per user from Settings -> Apps. Jira and Confluence share one Atlassian connection — a single Atlassian row covers both — made one of two ways, and an admin picks which under Settings -> Extensions -> Atlassian -> Manage: either each person signs in with their own Atlassian account from Settings -> Extensions, or the whole organization works through a single Atlassian service account. The two are still governed separately, so an admin can allow one and deny the other — see Atlassian extensions. Microsoft Teams is set up at the organization level — it requires a per-tenant bot registration coordinated with your IT admin, not a per-user connection. Admins decide which extensions your organization allows under Organization -> Extensions, either as a Ceiling that binds every role or as a Menu, where each role's own list decides; anything an extension needs configured (the Atlassian site and write switches, for example) stays on that extension's own page.
Beyond the extensions above, Strata includes a connector marketplace — dozens of additional third-party services (such as GitHub, Linear, Airtable, Dropbox, Cloudflare, Stripe, and PayPal) reached through the Model Context Protocol (MCP). An admin adds the organization's under Organization -> Connectors, and members find them under Customize -> Connectors; once a connector is on, the AI gains its tools and shows the connector's own logo in its action steps. See Integrations for the full catalog and how connectors are enabled.
How Strata fits an organization
- Microsoft SSO sign-in. No separate passwords; Microsoft handles authentication and multi-factor.
- Per-organization tenancy. Every organization gets its own users, conversations, settings, audit log, and saved connections — fully isolated.
- Admin-managed policy. Admins set the defaults new members start with (memory, conversation history, web search) and org-wide rules (conversation mode, data and audit retention, what may leave the organization), and can pin individual defaults with a padlock so members cannot override them. They also choose which AI models and extensions the organization can use, and can narrow those further per role or per individual user.
- Connectors that reach outside Microsoft. Jira and Confluence are Strata's first extensions that are not a Microsoft service or your own database, so an organization that connects Atlassian is reaching Atlassian Cloud alongside its Microsoft 365 tenant.
- AI that runs in your own tenant. Every organization connects its own Microsoft Azure AI Foundry from Organization -> AI engine. Every AI request about your data — chat, agents, documents, voice and the API — runs through that Foundry. The in-product help assistant is the sole exception: Kronisys hosts it.
The AI models
Strata draws from a central, curated Model Catalog rather than a fixed set of models. The catalog spans many models across OpenAI, Anthropic, xAI, DeepSeek, Mistral AI, Cohere, and Microsoft — every one served through Microsoft Azure AI Foundry. Each organization enables the subset of catalog models its members can pick from; admins manage this from Organization -> Models, where Manage models opens the Model Catalog to enable or disable each model.
The models a given person can actually use are the intersection of what the organization, their role, and their per-user settings allow. The in-app model picker (and the Model Catalog itself) is always the live source of truth for what's available to you.
For the full list and how selection works, see Models.
Where to go next
If you are a new user:
If you are an admin setting up a new organization:
- Onboarding your organization
- Signing in
- The Administration section (admin console reference, coming as the docs grow)
Reference
- Special code blocks — every rich block Strata can render in chat
- Callout reference — what each callout style signals
- Keyboard shortcuts
- Glossary
- Troubleshooting and FAQ
Support
- Status, security, and legal documents live at strata.kronisys.com.
- For help, write to support@kronisys.com.