Pilots for organizations
Try Locus with your team
Locus lets the AI assistant your people already use search the folders they choose, on their own computers, and cite the file for every answer. We run 60 to 90 day pilots with teams of 10 to 50 people. Pilot terms on request.
Who it is for
Teams whose answers live in documents, notes, PDFs and code on their own computers: research groups, consultancies, legal and finance teams, engineering teams. You need one person to run the pilot, and people comfortable installing a tool on their computer (macOS or Linux today).
What a pilot includes
- 10 to 50 seats for 60 to 90 days.
- One admin contact on your side, who invites people and can revoke a person's Locus API key.
- Written success criteria agreed before the pilot starts, and reviewed at the end.
- A shared channel (email or Slack) with the person who builds Locus.
- The free local engine for everyone; hosted features (managed embeddings, remote connection) where you choose to use them.
What is built, and what is not
Built today
- The local engine: it indexes the folders each person chooses and lets their AI assistant search them, with the file cited for every answer.
- Organization roles, invites, an audit log and revoking a member's API key.
- Managed embeddings and a remote connection through our relay, for people who want them.
Not built
- Online checkout for Teams. A pilot is agreed by email and invoiced by hand.
- A pooled or shared index. Nobody searches another person's computer.
- An uptime guarantee or a support SLA. The founder answers directly.
- Single sign-on and SCIM, and no audit report yet. A security overview is available on request.
Locus has no reference organizations to name yet. A pilot is how that changes, so we say so instead of showing logos.
Where your data goes, by mode
- Local engine
- 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.
- Your own embedding key
- Chunk text goes straight from your computer to the embedding provider you chose, under your own account.
- 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
- 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.
When your AI assistant searches, the matching excerpts go to that assistant, as they would if you pasted them in. Your raw files are never uploaded to Locus.
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.
A security overview is available on request.
How a pilot runs
Tell us about your team
Use the form below: team size, what the files are, and what a good result would look like.
Agree the success criteria
We write down what you will measure, and the pilot terms, which are available on request.
Run the pilot
Each person installs Locus on their own computer and indexes their own folders. We stay in the shared channel.
Review together
At the end we look at the criteria and decide together whether to continue.
Talk to us about a pilot
Pilot terms on request. We reply by email within two business days.
Prefer email? Write to yonilev2003@gmail.com.