Enterprise
Academe for institutions, labs, industry research, and national labs.
Research organizations evaluate Academe primarily on privacy. Where the data lives, who can see it, what the agents do with it, and how to leave. The answers are below, before any of the productivity claims.
Who this is for
Four research environments, one set of controls.
Universities and departments
Faculty, graduate students, and research staff working across multiple labs. FERPA-aware deployment, library SSO, and shared seat allocation across departments.
Research groups and labs
Single-PI labs and cross-institutional groups handling sensitive corpora. Data residency, IRB-friendly retention controls, and per-project tenant isolation.
Industry research
Corporate R&D, biotech, and applied-research teams. Tenant-isolated agents, document firewalls between projects, and contract-review-ready DPAs.
National labs and government research
Federally funded labs and agency research groups. On-premise and air-gapped deployment options, classification-aware retention, and FedRAMP-aligned posture.
Privacy and security
The questions your security team will ask, answered first.
Academe is built around the assumption that your research data is sensitive. Every control listed here is the default, not an upgrade.
Where your data lives
Encrypted at rest in your chosen region. US, EU, and Canada hosting available; sovereign-region options for national labs. We do not move data across borders without your explicit configuration.
Agents do not train on your data
Documents, prompts, drafts, and agent traces are never used to train any underlying model, ours or a provider's. Zero-data-retention is enabled with every model provider we route through.
Tenant isolation by default
Each institution and each project sits behind row-level security in Postgres. Agents only see what the requesting user has access to. No shared embeddings, no cross-tenant retrieval.
Compliance you can name
SOC 2 Type II in progress, GDPR-aligned, FERPA-compatible deployments for universities, HIPAA-ready posture for clinical research groups. We name the standard, not the adjective.
Bring your own keys
Route every model call through your own Anthropic, OpenAI, Google, or Azure account. Your provider, your billing, your audit log. Academe never sees the prompt content for BYOK requests.
On-prem and air-gapped options
For national labs and classification-sensitive groups, we deploy the full stack inside your environment. No outbound calls, your existing model provider, your existing identity store.
Export and deletion you control
Full data export at any time in machine-readable formats. Hard-delete on request honored within 30 days, with audit trail. Account closure removes everything, including derived embeddings.
Audit trail and access controls
SAML single sign-on, SCIM provisioning, role-based access by department or project, and admin audit logs your security team can ingest into the SIEM you already run.
Need a SOC 2 report, FERPA letter, or HIPAA BAA before procurement? Email the team and we will share the current set under NDA.
Support
The rest of the rollout details.
Volume seat pricing
Per-seat rates with volume discounts, one invoice, and department-level allocation when you need it.
Named support
A named onboarding partner and a direct line to the team building Academe.
Usage visibility
Admin dashboards, adoption reports, and per-department breakdowns for budget and rollout planning.
Procurement materials
Annual or multi-year agreements, purchase orders, local-currency invoicing, and a standard MSA.
Pilot before broader rollout
Run a structured pilot with a single department or lab before institution-wide deployment. Measurable adoption criteria agreed up front.
Migration and onboarding
Bulk import from Zotero, Mendeley, EndNote, and existing Overleaf or Google Drive corpora. Citation styles and reference databases survive the move.
Process
What happens after you contact us
01
Scope the rollout
We collect headcount, research use cases, data requirements, and expected timeline.
02
Review materials
We share security, privacy, compliance, and procurement documents for your review.
03
Start the pilot
Your team gets onboarding, admin setup, and a pilot plan before broader deployment.
Plan an institutional rollout.
Tell us your headcount, timeline, and procurement process. We will respond with next steps and the materials your team needs for review.