For Institutions
Research infrastructure your researchers actually want.
Built for researchers — and for the institutions that answer for them. A modern, governed writing workspace with EU data residency, audit built in, and procurement answers prepared before you ask.
Security by architecture
Encryption in transit and at rest, strict workspace isolation, role-based access, and immutable audit logs — the same controls on every plan, documented in full on the Security page.
EU data residency
All customer data — manuscripts, references, versions, backups — is stored and processed in AWS eu-west-1 (Ireland). Nothing about residency changes with scale.
Research integrity, evidenced
Versioned manuscripts, ORCID-linked attribution, and exportable AI usage reports give integrity offices records instead of recollections when questions arise.
No lock-in, contractually and technically
Every manuscript exports to DOCX, PDF, and LaTeX; every library to BibTeX — on any plan, at any time, including after termination. Exit is a feature, not a negotiation.
The full control set — encryption, isolation, audit logging, AI data handling, and sub-processors — is documented on the Security page.
Identity & access
Enterprise identity, stated honestly.
We mark what ships today and what is on the roadmap — so your IT review is based on the product as it is, not as a datasheet wishes it were.
ORCID sign-in
Researchers authenticate with the identity they already use for publishing. Attribution is correct from the first session, with no directory work on your side.
SSO via SAML 2.0
Institution-wide single sign-on through your existing identity provider (Entra ID, Okta, Shibboleth). In development for institutional rollouts — pilots do not depend on it.
SCIM provisioning
Automatic provisioning and deprovisioning from your directory, so access ends when affiliation ends. Scheduled to follow SAML SSO.
For IT administrators
Simple to run today. Directory-native on the roadmap.
Everything below the line ships now; everything on the roadmap is badged that way here and everywhere else we describe it.
Running today
Invite-based provisioning
Members join a workspace by email invite or ORCID sign-in. Admins manage membership, roles, and removal from one panel — access ends the moment an admin removes the account.
Workspace policy controls
AI features can be enabled or disabled per workspace, every export and permission change lands in an append-only audit log, and admins can review activity without reading anyone's research.
No client software
Dissertatio is a web application — nothing to package, image, or patch on managed devices. TLS 1.2+ everywhere; no browser extensions required.
Identity roadmap
SAML 2.0 SSO
Institution-wide single sign-on through Entra ID, Okta, or Shibboleth — in development, and not a pilot dependency.
SCIM provisioning
Directory-driven provisioning and deprovisioning, so access follows affiliation automatically. Scheduled after SAML SSO.
Domain capture
Accounts created with your institutional email domain surfaced to your admins for consolidation under the institutional agreement.
Deployment
Pilot, department, institution — in that order.
The credible path runs through one lab that stops emailing drafts. Every stage scales under the same terms, so nothing has to be re-procured.
Weeks 1–4
Pilot lab
One lab, real manuscripts. We provision the workspace, import the group's reference library and templates, and hand your IT team the security pack in parallel — so the technical review and the writing happen in the same month. Success looks like a lab that has stopped emailing drafts.
Term 1
Department
The pilot's usage report and the lab's own account carry the decision. A department agreement adds seats under the same terms — per-seat annual pricing, purchase-order support, onboarding sessions for each lab as it joins. No re-procurement.
Year 1
Institution
An institution-wide agreement brings the research office and IT into a defined rhythm: a named contact, scheduled service reviews, SSO rollout as it ships, and integrity-office access to the records that make investigations short.
For research offices
Integrity questions answered from records.
The office that answers for research conduct gets the evidence layer researchers generate just by writing.
Records instead of recollections
Versioned manuscripts and ORCID-linked attribution mean authorship questions and integrity reviews start from an evidence trail, not from interviews about who wrote what, when.
Disclosure-ready AI logs
Every AI interaction on a manuscript is logged and exportable as a per-manuscript AI usage report — the document journals increasingly ask for, generated from the record rather than from memory.
A pipeline you can see
Lab workspaces show every manuscript's stage — drafting, in review, validated, submitted. During pilots and service reviews, research offices receive usage summaries that show output without surveilling researchers.
Procurement
Ready for the questionnaire before it arrives.
Procurement should be the boring part. We keep the answers current so a pilot is a decision, not a project.
Documentation on request
Security overview, architecture summary, data-flow description, and sub-processor list — prepared for review boards and IT security questionnaires.
Data Processing Agreement
A GDPR Article 28 DPA with documented sub-processors and advance notice of changes. Hashtag AI Labs acts as processor for institutional deployments.
Straightforward commercial terms
Per-seat pricing, annual invoicing, and purchase-order support. Pilots start with a single lab and scale to departments without re-procurement.
The compliance pack, itemized
What we hand your review board, IT security, and DPO — available on request from institutions@hashtagai.io.
- Data Processing Agreement — GDPR Article 28, with documented sub-processors — signed with every institutional agreement
- Security questionnaire pack — Prepared answers for standard IT security questionnaires, current at request time
- Architecture & data-flow diagram — How a manuscript moves through the system, including exactly what AI checks can read
- Sub-processor list — Published openly on the Security page, with advance notice of changes to admins
- AI data-handling statement — The no-training guarantee, logging, and admin controls, stated for review boards
- Support & service terms — Response targets, escalation paths, and review cadence for institutional customers
See the full pack — including our SOC 2 and WCAG 2.2 AA accessibility roadmap, badged honestly — on the procurement pack page.
Data processing
Clear answers for your DPO.
- Controller / processor
- For institutional deployments, the institution is the data controller and Hashtag AI Labs is the processor, operating under a signed DPA.
- Residency
- All customer data is stored and processed in AWS eu-west-1 (Ireland), including backups.
- Sub-processors
- A short, documented list — cloud infrastructure, AI model provider, payments — with advance notice before any change. The current list is published on the Security page.
- AI data handling
- Manuscripts are never used to train models. AI features can be disabled workspace-wide by administrators, and every AI action is logged.
- Data-subject rights
- Access, export, and deletion are product features: researchers and admins can exercise them directly, without a support ticket.
Support
Support commitments, in writing.
Institutional agreements define response targets and escalation paths — not best effort.
Priority support
Institutional customers get a dedicated support channel with a one-business-day first-response target, ahead of the standard queue.
Onboarding & rollout
Structured onboarding for pilot labs — workspace setup, template migration, and reference-library import — plus training sessions for research offices.
Named contact & reviews
Department-wide agreements include a named contact and scheduled service reviews covering usage, incidents, and the product roadmap.
Procurement FAQ
The questions that decide a pilot.
- What does a pilot cost, and what are we committing to?
- A pilot runs on standard Lab pricing for the pilot lab's seats — no institution-wide commitment, no setup fee. If the pilot does not convince the lab, it ends there: every manuscript exports to DOCX, PDF, or LaTeX and every library to BibTeX.
- Do you sign our DPA, or provide your own?
- We provide a GDPR Article 28 Data Processing Agreement with a documented sub-processor list and advance notice of changes. Institutional riders and amendments are reviewed case by case with our counsel — send them with your first questionnaire.
- Where is our researchers' data, and can we verify the controls?
- All customer data is stored and processed in AWS eu-west-1 (Ireland), encrypted in transit and at rest. The security pack — architecture summary, data-flow diagram, control descriptions — is available on request, and the Security page documents the control set publicly.
- Can we deploy before SSO ships?
- Yes — pilots and department rollouts run on ORCID sign-in and email invites today, which is how researchers already authenticate for publishing. SAML SSO is in development and marked as roadmap above; institutional customers get timeline updates in service reviews. We will not sell it as shipped until it is.
- Who needs a paid seat?
- Seats cover members of shared lab workspaces. External collaborators are unlimited and free on every plan — a co-author at another institution joins any manuscript at no cost, which matters for multi-site projects and consortia.
- What happens to the data when a contract ends?
- Export is a product feature, not an off-boarding negotiation: manuscripts to DOCX, PDF, and LaTeX, references to BibTeX, plus version history and audit records — available before, during, and after termination. Deletion then follows the timelines in the DPA.
Bring Dissertatio to your institution.
Tell us about your labs, your identity setup, and your procurement process — we will reply with documentation and a pilot proposal within two business days.
Or write directly: institutions@hashtagai.io