Structured records, files and search in one place, with the roles, access rules and activity log a team needs — on your own infrastructure.
Equipment in a spreadsheet, contracts in a drive, specs in a wiki: every question starts with “where is it”.
Collections with your own fields, files attached to the record, links between records across collections, and one search over everything a person may see.
Coarse access forces you to pick between exposure and a bottleneck.
Workspace roles with separate permissions; per-collection rules by field value; and edit rights for single fields, so a role can change “status” but not “price”.
A copied database or a backup should not be a data breach.
Encrypted collections: titles and values are stored as ciphertext under a key protected by the collection password. It guards against stolen storage and backups; it is not end-to-end, and we say so.
Without a trail, every dispute about a record is an argument.
An activity log per workspace and per collection with filters, CSV export and retention. Titles of protected records are withheld from the log itself.
Onboarding by shared password and offboarding by hope is how access outlives employment.
Invitations by e-mail, a list of devices with remote sign-out, moderation (ban, restore, erase) and API keys with an expiry.
A parts list or a reading list for partners usually means a PDF that is stale a week later.
Publish a collection as a read-only registry; others can browse it or fork it into their own workspace. Personal fields never leave.
Recordings of the real interface. Point at one to play it.
Hover to playInvite people, give them roles, and decide exactly what each role can change. A tester can flip the status of an entry without being able to rename it or touch the price.
Hover to playFor material that should not sit on disk in the clear: a collection is locked with its own password, and what is stored — titles and values — is ciphertext.
Hover to playMark a collection as a public registry to let others browse it read-only, and clone any registry into your own workspace to make it yours.
Each instrument is a record: inventory number, location, responsible person, calibration date, the manual as a PDF, photos. A technician role can change “location” and “calibration date”; only the manager can edit the rest.
Datasets sit in an encrypted collection that only two people can unlock. The activity log shows who changed what; a public registry lists the instruments other labs may borrow.
Requirements, drawings and test results attached to each item, with release status only some roles may change.
Footage, audio and documents per project, with a review status that reviewers can change and nothing else.
Contracts, requirements or licenses as records with files, links between them and an audit trail.
Also: For yourself · For self-hosters