Your mail, your servers
A real mail platform, not a forwarding layer: SMTP and IMAP we operate, with DKIM, SPF, DMARC and TLS reporting configured properly rather than left as an exercise.
An office suite on infrastructure you control.
Mail, documents, spreadsheets, slides, chat and file storage — built as one system rather than assembled from acquisitions. One directory, one permission model, one sync protocol underneath all of it.
Talk to us Currently in private trials.
Documents that collaborate
Spreadsheets, documents and slides edited by several people at once, with conflict-free merging and presence — the same editing model the large suites use, without the surrounding sprawl.
Files, shared like documents
Content-addressed storage with versioning and per-file sharing, using the same groups and roles as everything else. Nothing to reconcile between two products.
One directory
People, groups, roles and licences in one place, with an audit log that cannot be edited — including by an administrator. Sign-in is ours; other providers can be attached to an account rather than replacing it.
Why this exists
One model, not five
The large suites grew by acquisition, so permissions, search and sync differ per application. Lattice has one directory and one permission model across mail, documents and files, which is why sharing behaves the same everywhere.
Nothing leaves your tenant
No content is used to train anything. The audit log is append-only at the database level, so what happened to a document is a matter of record rather than assurance.
Licensing you can read
Products and tiers, seats assigned to people. What a licence grants is enforced when a token is issued, not described in a table somewhere.
Where it is today
Lattice is early and in private trials. Mail, the editors, storage, identity and administration are running in production; some of the suite is further along than the rest, and we would rather say so than find out together later. If that is interesting rather than disqualifying, we should talk.