Flintyst connects Slack, Drive, Confluence, Jira and dozens more, then answers questions in plain language with every claim cited. It only uses what each person is already allowed to see, and it keeps up as your tools change.
Answers stream here, with a numbered citation on every claim.
Pick a question, press / to type your own, and hover a citation to see the exact passage.
Reads from the tools your company already writes in
The problem
Decisions live in threads, specs in wikis, context in tickets and the final word in someone's inbox. Every question becomes a scavenger hunt across six tools and two colleagues.
Search Slack for “EU residency”212 results
Three pages called “Data residency”Which is current?
DPA addendum v2 (final) (1).docxOr is it v3?
“Does anyone know…?” in #eng-platformWaiting
“Check the ADR, I think”17 min later
Find ADR-031, unsure it's the latest46 min gone
What did we decide about EU data residency?
Pinned to eu-central-1 for enterprise tenants 1, including indexes and backups 2, with the dedicated cluster due 28 November 3.
Connected sources
Connectors sync documents, messages, tickets and code into a single index, along with who is allowed to see each one. Click any source to see what it pulls and how its permissions come across.
1,231,167documents indexedWhat's inside
Retrieval, ranking, permissions and citations are the product. The chat window is just where you meet them.
Every sentence points to the passage it came from. Hover a number and the quote lights up in its source.
The on-call rota changes on Monday 1 and swaps are made in PagerDuty, not Slack 2. Marco covers the first week 3.
Keywords for exact names and IDs. Vectors for meaning. Both, reranked.
Incremental syncs every few minutes, so this morning's decision is already searchable.
Sometimes you want the document, not a summary. Filter by source, author and date.
Q4 pricing change: FAQ0.94
Pricing deck v120.88
#pricing decision thread0.81
Mention the bot in any channel. The answer lands in the thread, cited.
JTJonah @flintyst what's the VPN for the Lisbon office?
Flintyst Use the eu-south profile in the VPN client 1. Setup steps are in the IT guide 2.
Thumbs up or down on an answer adjusts how its sources rank next time, and admins see which questions went unanswered.
ADR-031: EU data residency▲ boosted
Data residency FAQ (2023)▼ demoted
DPA addendum v3▲ boosted
Old pricing deck v9▼ demoted
Put cited answers inside your intranet, your support desk or your own tools.
# Illustrative request
curl -X POST https://flintyst.techyst.net/api/ask \
-H "Authorization: Bearer $FLINTYST_KEY" \
-d '{"question": "Who owns billing?"}'
→ { "answer": "The payments team…", "citations": [3] }How an answer is made
Nothing mysterious happens between the question and the answer. Step through it, and watch the reranker throw out a page that only looked relevant.
The question is parsed for intent, entities and time, then expanded with the terms your company actually uses.
“What did we decide about EU data residency for enterprise customers?”
Expanded with +gdpr +eu-central-1 +data location
Permission-aware
Flintyst checks each source's own access rules before retrieval, so the model never reads what the person asking couldn't open themselves. Switch who's signed in and ask again.
Where are we on the Northwind renewal, and what's blocking it?
Cited · 3
3 sources hidden: no access
Shown here for the demo. In Flintyst, sources you can't open never appear at all.
Custom assistants
Give each team an assistant with its own instructions, its own document sets and its own audience. Pick one to see it answer.
Can I expense a co-working day pass when I'm travelling?
Across the company
The questions change by team. The shape of the answer doesn't: direct, current and cited.
Stop re-deriving decisions from old threads. Find the ADR, the PR and the incident that explain why the code looks the way it does.
Why did we move session storage off Redis?
Memory pressure during the March incident; ADR-024 chose Postgres with a TTL index. 1
ConfluenceJira
Who owns the billing service now?
The payments team since the Q2 re-org; Marco is the tech lead. 1
ConfluenceSlack
Is there a runbook for rotating the TLS certs?
Yes, in SRE runbooks, and it was updated after last month's renewal. 1
ConfluenceGitHub
Answer the security questionnaire before the call ends. Know what was promised to a customer without digging through a colleague's inbox.
Do we have a SOC 2 Type II report I can share?
Yes, the 2026 report is available under NDA from the trust folder. 1
Google DriveConfluence
What discount did Contoso get at renewal?
15% on a two-year term, approved by the CRO in June. 1
SalesforceGmail
Which customers use us with Entra ID?
Eleven accounts, listed in the SSO field on their opportunities. 1
Salesforce
The fix for this ticket is usually in a ticket someone else closed last month. Find it, with the steps that worked.
Customer can't reset 2FA. What's the process?
Verify identity with the account owner, then reset from the admin console. 1
ZendeskConfluence
Is the CSV import bug fixed in 4.19?
Yes, fixed in 4.19.1; the workaround is no longer needed. 1
JiraWeb crawl
What do we say about data deletion requests?
Deletion within 30 days, confirmed by email; use the GDPR macro. 1
ZendeskConfluence
The same fifty policy questions, answered from the current handbook in every country, without a ticket to People Ops.
How many sick days do I get in Portugal?
Statutory sick leave applies from day four; Acme covers the first three. 1
Google Drive
When is the next compensation review?
October, with changes effective from 1 January. 1
NotionSlack
Can I work from another country for a month?
Up to 30 days a year, with manager approval and a tax check. 1
SharePointNotion
Read the state of the company from the record itself. Ask across deals, tickets and plans without waiting for a status deck.
What are the top three reasons deals slipped this quarter?
Security reviews, procurement timing and SSO requirements. 1
SalesforceGmail
Which Q3 goals are at risk?
EU cluster and self-serve onboarding; both flagged in the last review. 1
Google DriveJira
What did customers complain about most last month?
Export speed and SSO setup, from 212 tickets tagged by theme. 1
Zendesk
The job
Answer model
Which runbook covers a Postgres failover?
Asked in On-call Helper · answered by FastBest fit for this job. Short, factual answers from one or two passages. Speed matters more than depth here, and it is the cheapest model per answer.
Every model answers only from retrieved passages, with citations. Figures are illustrative.
Choose the model that fits
A quick lookup doesn't need the biggest model, and a contract review shouldn't get the smallest. Pick a job, try a model, and see the trade-off in quality, speed and cost.
From kickoff to company brain
A typical rollout, run with our team alongside yours. Scroll through it.
We create your Flintyst workspace, connect single sign-on through your identity provider, provision people and groups, and agree on admin roles with you.
Workspace setup · Acme
Workspaceacme · created
Sign-inOkta · SAML
People and groupsSCIM · 1,240 people
Admin roles4 admins · 2 auditors
Answer modelsBalanced · per assistant
Start with the three tools people search most. Each connector is authorised by its own admin, with read-only scopes.
Connectors
SlackConnectedOAuth · read-only
ConfluenceConnectedAPI token · 14 spaces
Google DriveConnectedService account · domain-wide
JiraConnectedOAuth · 9 projects
SalesforcePendingWaiting for admin consent
History is indexed once, then kept current with incremental syncs. Permissions come across with every document.
First full indexETA 3h 10m
Permissions indexed alongside every document
Map groups to document sets and give each team an assistant with instructions that fit how it works.
Groups → document sets
Open it to the company. Feedback and unanswered questions show which pages to fix and which sources to add next.
Questions per day · first monthIllustrative
Top unanswered this week
Where is the brand font licence?add a source
What's the SLA for Enterprise support?add a source
The difference
Every tool has its own search. None of them knows what the others say, which version is current, or who is allowed to see what.
Control
OIDC or SAML through your identity provider. People are who your directory says they are.
Access rules come across from each source with the documents, and are checked again on every query.
Who asked what, which assistant answered and which sources it used, kept as long as your policy says.
Documents, embeddings and questions are encrypted in transit and at rest, and connector tokens are stored encrypted.
Your documents and questions are not used to train anyone's model, whichever model answers.
Daily backups verified by restoring them, monitored uptime, and a full export of settings and history whenever you ask.
priya.nOn-call Helper3 sources
diego.mSales Engineer4 sources
sam.kGeneral1 source · 5 filtered
lena.wHR Policies2 sources
marco.rGeneralno match
aisha.kOnboarding Buddy2 sources
jonah.tSlack bot3 sources
FAQ
If your question isn't here, ask us. A person who works on Flintyst every day will answer, with sources.
Most teams ask their first real questions within a week. We set up your workspace and single sign-on, connect the first sources with you, and the full index builds in the background. A company-wide rollout typically takes about three weeks.
Slack, Google Drive, Confluence, Jira, GitHub, Notion, Salesforce, Zendesk, SharePoint, Gmail, Microsoft Teams, Linear, Dropbox and more, plus web crawls and file uploads. Each connector is authorised by that tool's own admin, with read-only scopes.
Yes. Use a fast model for quick lookups, a deeper one for analysis or a long-context model for contracts and reports, and set a different one for each assistant. You can switch later without re-indexing, and every model answers only from retrieved passages, with citations.
Where a source exposes its access rules, Flintyst syncs them with the documents and checks them on every query. Someone who can't open a file in Drive won't get an answer built from it.
For everything else, you scope access with groups and document sets.
Answers are generated only from retrieved passages, and every claim carries a citation you can open. When the index doesn't cover a question, Flintyst says so instead of guessing. You can still judge an answer, and now you can check it in one click.
Most connectors sync incrementally every few minutes, and some pick up changes as they happen. Each source shows when it last synced, and admins can trigger a sync at any time.
No. Your documents and questions are never used to train anyone's model, whichever model you choose. Everything is encrypted in transit and at rest, and every query is recorded in an audit log your admins can review.
Pricing isn't per seat, so giving the whole company access costs the same as giving it to one team. Ask us for a quote.
Yes. Mention the bot in a channel or send it a direct message and it answers in the thread, with the same citations and the same permission checks as the web app.
Yes. The API returns the same cited answers as the web app, so you can add them to an intranet, a support desk or an internal tool. Every request is checked against the permissions of the person asking.
Connect your first three sources, ask the question your team has been chasing all week, and check the citations yourself.