The research memory your team keeps losing. Kept. Cited. Administered.
Give the team one library. Everyone asks in scoped chat and gets the exact passage back — owners get roles, SAML SSO, SCIM provisioning, and an exportable audit log.Replies from a human, usually within a day.Roles, seats, SSO — administered, not improvised.
Invite the team, set roles, and watch every change land in the audit log.
Five roles, enforced in codeFive roles. Sixteen capabilities. Enforced in code, not in a PDF.
Every mutation checks the capability table before it runs.
Authorization layer — workspace capabilities
assertWorkspaceCapability(userId, workspaceId, capability) guards every workspace mutation — sixteen capabilities across five roles, covered by the capability, seat-cap, and invite-lifecycle test suites.
Sign-in your IT team already trusts.
- SAML 2.0, SP-initiated
- SCIM 2.0 provisioning
- WebAuthn step-up on sensitive actions
- One-click session revocation
Publish the canon once. Everyone asks it, cited.
Managed, read-only sources your whole workspace can attach and question.
Attached boxes stay read-onlyDrive, Gmail, and Zoho arrive with their source.
Imports keep a source badge and link back to the original record.
Filter the library by where notes came fromYour library is yours. The workspace is a choice.
Personal libraries stay personal — admins cannot read members' private notes.
Workspace content isolation — tested at the database layer
Content isolation between personal libraries and workspaces is enforced in the data layer and pinned by integration tests — not a settings toggle, a contract.
Sharing into the workspace is per-folder and opt-in, never a default.
Folder-level sharing — explicit, revocable grants
A member chooses a folder and shares it; the grant is explicit and revocable. Everything else stays private. Every change lands in the hash-chained audit log.
Bring your security review. We answer it.
US-hosted. EU residency is on the roadmap. Customer content is never used to train models.Plans
The answers procurement asks for
What does the Team plan include?
Everything in Pro for every seat, plus a shared workspace with five roles, an admin console for invites and seat caps, SAML SSO with SCIM provisioning, hash-chained audit log export, and knowledge boxes for managed sources. $24 per seat per month, monthly-only.
Do you support SSO and SCIM?
Yes — SAML 2.0 (SP-initiated) single sign-on and SCIM 2.0 user provisioning. We run identity-provider setup with you during pilot onboarding: Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud, or any generic SAML IdP.
Can workspace admins read members' personal notes?
No. Personal libraries stay personal — workspace content isolation is enforced at the database layer and covered by integration tests. Sharing into a workspace is per-folder and opt-in, never a default.
Do you offer invoices or longer-term agreements?
Billing is monthly-only at launch. Organizations that need invoices or a custom agreement can email us — we answer every note personally and route you to the right paperwork.
Where is data hosted?
US-hosted today. EU data residency is on the roadmap for enterprise workspaces — tell us if that gates your pilot and we will keep you posted honestly.
Is customer content used to train models?
No. Your library is yours: answers are grounded in your saved sources with citations, and export to Markdown and JSON stays available at all times.
