Locus for teams
Cited answers from your own files, in every team
Every person's own files become cited answers in the AI assistant they already use. Each answer names the file it came from, so anyone can check it.
Your raw files are never uploaded to Locus. When your AI assistant searches, the matching excerpts go to that assistant, as they would if you pasted them in.
Built to roll out one person at a time: each computer indexes its own folders, and there is no pooled index of your company's documents.
Use cases
Any team can ask questions of the files it already has
Each person points Locus at the folders they work in: local folders, a synced folder, or a network share IT already mounts. A few examples of what to use it for:
Engineering
- Find where a design decision was made across design docs, ADRs and READMEs, with the file to open.
- Ask how a service is configured and get answers drawn from the repository's code, YAML and runbooks.
- Pull the steps from past incident write-ups when the same alert fires again.
- Onboard faster by asking questions of the team's docs folder instead of searching it by hand.
Legal
- Find which agreements in a folder of signed PDFs mention a given clause, and open each one.
- Compare how past contracts worded a limitation of liability, with the source file for each version.
- Check an internal policy against what earlier memos said, citing the memo.
- Answer a colleague's question from the playbook with the exact document behind it.
Consulting and research
- Search years of past deliverables and interview notes for a client question you have answered before.
- Gather every note that mentions a company, market or method, with paths you can check.
- Draft a literature summary whose every claim points back to a paper in your folder.
- Reuse your own frameworks without digging through old project folders.
Sales and customer success
- Answer a security or product question from past proposals and RFP responses, citing the source.
- Prepare for a renewal by asking your account notes what was promised and when.
- Find the case write-up or support note that matches a customer's problem.
- Keep answers consistent by quoting the approved document instead of memory.
Product
- Ask what users said about a feature across interview notes and research reports.
- Trace a requirement back to the spec or decision record that introduced it.
- Summarize open questions across a quarter's planning documents, with the files linked.
- Check whether an idea was already explored, and read why it stopped.
Operations and HR
- Answer "what is our process for…" from the handbook and procedures folder, citing the page.
- Find the current version of a policy among older copies, and see which file says what.
- Pull vendor terms and renewal notes together before a review.
- Help a new hire find answers in the onboarding documents on their own.
Finance
- Find the board memo or report where a budget assumption was set.
- Search CSV exports and PDF reports for a figure, and open the file it came from.
- Check what an expense or procurement policy says before approving an exception.
- Collect the documents behind a number when an auditor asks for them.
Locus reads PDFs with a text layer, Word documents (.docx), Markdown and plain text, CSV, HTML, JSON and YAML, and source code. Spreadsheets (.xlsx), slide decks (.pptx) and scanned images are not read yet.
How it works
One Locus per person, no pooled index
Each person installs Locus
On their own computer, pointed at the folders they work in. Locus reads them under that person's own operating-system account, so it can reach only what that person can already open.
Their AI assistant searches through MCP
Locus answers the assistant's searches from that person's own index. Every result carries its file path and position, so the answer can cite the exact file.
The organization layer sits on top
Roles, invites, an audit log and key revocation. The organization layer adds identity and control; it never adds a shared index.
Because each person indexes their own copy, a lost or compromised laptop exposes what that person could already read, now searchable. Full-disk encryption and prompt key revocation are the controls for that case.
Pilot with us
Try it on your team's real files first
Locus is new, and we have no enterprise customers to quote yet. Instead of logos, we offer a founder-led pilot: a small group, their own files, and an honest review of what worked.
Scope it together
A short call to pick a small group, the folders they already work in, the AI assistants they use, and the questions that matter to them. We write down what a good result looks like before anyone installs anything.
Set up with the founder
Each person installs Locus on their own computer, with the founder on hand to help. We recommend the local embedder for a company pilot, so indexing does not send chunk text over the network.
Use it on real work
People ask their usual AI assistant questions about their own files for a period we agree with you up front, and we check in along the way.
Review what happened
We go through the results with you and you decide whether to continue. Nothing about a pilot commits you to buy.
What we measure together
- Whether answers to your team's real questions were correct and cited the right file
- How long setup took on each computer, and what got in the way
- Which AI assistants and folders people actually used
- What your security or procurement reviewers asked for that we could not provide yet
Controls
What admins control today, and what is planned
Every item is labelled. Planned and not-built items have no committed date; tell us which ones your procurement needs, because that decides what we build next.
Access and identity
Who is in the organization, and how they sign in.
Organization, roles and invites
Available todayAn owner creates the organization at /dashboard/org and invites colleagues by email. Roles are owner, admin and member; invites expire.
Sign-in
Available todaySign-in is through Supabase, with Google or GitHub.
Single sign-on and SCIM
PlannedSAML or OIDC single sign-on and SCIM provisioning. Not built yet.
More than one owner
PlannedToday each organization has exactly one owner. Shared ownership is not built yet.
Monitor and audit
What admins can see, and what they cannot.
Audit log and invites
Available todayAdmins can see the organization's audit log and its pending invites in the dashboard.
Who sees what
Available todayIf you join an organization, its members can see your email, your role, when you joined, whether you are still a member, when you last used Locus's hosted features and which Locus version you ran. Its admins can also see its invites and audit log, and can revoke your Locus API keys. Nobody in the organization can see your files or searches, because Locus doesn't store them.
Audit log export
PlannedExporting the audit log to your own logging or SIEM tool. Not built yet.
IP allowlist
Not built yetRestricting Locus's hosted features to your company's network addresses. Not built yet.
Offboard and scale
Removing access, and how capacity is counted.
Admin key revocation
Available todayAn admin can revoke a member's Locus API keys, for a departing colleague or a lost laptop, without removing them from the organization. A revoked key is refused on its next request; a relay token already issued from it stays valid for up to ten minutes.
No pooled index
Available todayEach person's Locus indexes only the folders on their own computer, under their own operating-system account. There is no shared index of your company's documents on our servers.
Indexing power per seat
Available todayEach seat on managed embeddings has its own daily indexing limit, set by its plan. With the local embedder, indexing runs on the computer and uses none.
Pooled indexing power
PlannedOne shared indexing-power budget for the whole organization instead of one per seat. Not built yet.
Data residency
Not built yetA choice of region for the account data and relay traffic that pass through Locus's hosted services. Not built yet.
Support
Who helps you, and how fast.
Founder-led setup and support
Available todayLocus is run by its founder today, who works with each pilot directly. We reply by email within two business days.
Priority support
Not built yetA support plan with agreed response times. Not built yet; there is no on-call rotation today.
Not a fit yet if you need, today:
- single sign-on (SAML or OIDC) or SCIM provisioning
- access control that mirrors different permissions on different subfolders of a share
- centrally managed installs and configuration across a fleet; today each person follows the setup guide
- Windows: Locus runs on macOS and Linux, and Windows is not yet verified
- a SOC 2 report or an ISO 27001 certificate: we have neither, and no audit has been performed yet
Tell us anyway. More detail on what the organization layer does today.
Security and trust
What protects your data, and what we don't have yet
Indexed on each computer
Locus reads files where they are, under each person's own account, and keeps its index in a folder only that account can read. Your raw files are never uploaded to Locus.
No training on your data
We don't use your files, chunk text or searches to train models. On managed embeddings, Voyage AI embeds chunk text under its own terms: Under Voyage AI's standard terms, Voyage may keep the text it receives and use it to train its models unless the account holder opts out; with the opt-out on, Voyage deletes the text once it has processed it. We have not yet confirmed that opt-out for Locus's account, so for now assume Voyage may keep chunk text and search queries sent through managed embeddings. The local embedder avoids this entirely.
Keys stored as hashes
Locus API keys are stored only as hashes, never in plaintext, and every account-data table is protected by row-level security in our database.
Encrypted in transit
Locus's website, embedding relay and remote-connection relay are served over HTTPS (TLS). Content passing through the relays is not stored.
Web AI app tokens confined
When web AI apps connect through OAuth (not open yet), the token they receive is refused by every table and function in our database; only the relay can act on it. That confinement is already live in production.
SOC 2: aligned, self-assessed, not audited
Aligned with the SOC 2 Trust Services Criteria: self-assessed, not audited or certified. No auditor has reviewed our control map and no SOC 2 report exists. A SOC 2 Type I report is our target for 2027, not a commitment.
A DPA, on request
A data processing agreement is available on request, and our sub-processors are listed publicly.
No penetration test yet
No penetration test has been run. There is no dedicated security team or on-call rotation. We will tell you which controls exist and which don't before you sign anything.
What leaves each computer
- Local embedder
- Indexing and embeddings run on your computer. When your AI assistant searches, the matching excerpts go to that assistant, as they would if you pasted them in.
- Managed embeddings
- On managed plans, chunk text and your search queries pass through Locus's relay to Voyage AI to be embedded. We don't store them; we keep only usage counts.
- Remote connection (in testing)
- When you reach your computer from another device or a web AI app, your question and the matching excerpts travel through Locus's relay (Vercel and Supabase) to and from your computer. They are encrypted in transit and we don't store them.
- Always
- Your raw files are never uploaded to Locus.
Integrations
The AI clients your people already use
Locus speaks MCP, the open standard for connecting tools to AI models. Locus works with Claude Code, GitHub Copilot CLI, Codex, Claude.ai (web app) and ChatGPT (general chat, not Codex), with cited answers. Claude.ai and ChatGPT connect through Locus's hosted relay. The connect guide has setup steps for more clients, each labelled with how far along it is:
Works with: 5 clients
We asked real questions through this client and saved the answers, which cited at least two files.
Connects: 12 clients(Not yet verified)
We saw this client connect to a real Locus server. We have not yet recorded it answering questions.
Setup guide: 12 clients(Not yet verified)
Setup steps written from the vendor's own docs. We have not yet finished a connection check with this client.
Web and phone AI apps reach a person's computer through the Locus relay; that connection is in testing. See every client and its level and the connect guide.
A small team that pays by card? Look at Teams first.
Teams is for 3 or more people: one bill, no procurement. Each member's Locus indexes only their own computer, and who sees what is the same as in any organization: If you join an organization, its members can see your email, your role, when you joined, whether you are still a member, when you last used Locus's hosted features and which Locus version you ran. Its admins can also see its invites and audit log, and can revoke your Locus API keys. Nobody in the organization can see your files or searches, because Locus doesn't store them. Teams seats cannot be bought online yet. Paid plans are not open yet. Teams
FAQ
Questions buyers ask
What leaves each person's computer?
Your raw files are never uploaded to Locus. What does leave depends on the mode. Local embedder: Indexing and embeddings run on your computer. When your AI assistant searches, the matching excerpts go to that assistant, as they would if you pasted them in. Managed embeddings: On managed plans, chunk text and your search queries pass through Locus's relay to Voyage AI to be embedded. We don't store them; we keep only usage counts. The full breakdown, mode by mode, is on the privacy page.
Can an admin, or anyone else in the organization, search my files?
No. There is no shared index: each person's Locus searches only the folders on their own computer. If you join an organization, its members can see your email, your role, when you joined, whether you are still a member, when you last used Locus's hosted features and which Locus version you ran. Its admins can also see its invites and audit log, and can revoke your Locus API keys. Nobody in the organization can see your files or searches, because Locus doesn't store them.
Which AI assistants does it work with?
Locus connects through MCP, the open standard many AI clients support. Locus works with Claude Code, GitHub Copilot CLI, Codex, Claude.ai (web app) and ChatGPT (general chat, not Codex), with cited answers. Claude.ai and ChatGPT connect through Locus's hosted relay. The compatibility page lists every other client with how far along it is.
Which computers does it run on?
macOS and Linux. Windows is not yet verified.
What happens when someone leaves the company?
An admin revokes their Locus API keys and removes them from the organization. Their local index is a folder on their computer, so it goes wherever that computer goes: wipe or reassign the laptop as you would for any other local data.
How much does it cost?
We don't publish an enterprise price; we quote it after we understand your team and setup. A small team that pays by card can use Teams: 3 or more seats, with seat pricing on request; seats cannot be bought online yet. Paid plans are not open yet.
Can we run a pilot first?
Yes. A pilot is a small group using Locus on their own files for a period we agree up front, set up with the founder, with results reviewed together at the end. Use the form below to start.
Do you have a SOC 2 report?
No. Aligned with the SOC 2 Trust Services Criteria: self-assessed, not audited or certified. No auditor has reviewed it and no SOC 2 report exists. A Type I report is our target for 2027. If your procurement needs a report, say so in the form: it tells us what to prioritize.
Will you fill in our security questionnaire?
Yes. We keep a written control matrix and a standard answer set, and where a control is missing, the answer says so. A DPA is available on request.
Which languages does search handle?
The free local mode is optimized for English; managed mode uses a multilingual model. We have not yet measured search quality in other languages.
Can we use it without a Locus account, fully on our own computers?
Yes. The local engine with the local embedder needs no account and no API key; indexing and embeddings run on each computer. You lose the organization layer and managed embeddings. Search results still go to the AI assistant each person chose.
Can people reach their files from a web AI app or a phone?
That connection is in testing. When you reach your computer from another device or a web AI app, your question and the matching excerpts travel through Locus's relay (Vercel and Supabase) to and from your computer. They are encrypted in transit and we don't store them. Only one computer per account serves remote requests at a time; starting Locus relay on another computer takes over. The computer must be on, awake and running Locus. Remote connection needs an active subscription or trial.
Talk to us
Leave your details
Tell us about your team and what you need: a pilot, a quote, or answers for your security review. We reply by email within two business days.
Prefer email? Write to yonilev2003@gmail.com with your team size and what you need from procurement.
Nothing on this page is a binding offer. Pricing, compliance posture and access-control scope are agreed in writing before any contract.