OpenRegister
Schemas, registers, structured data objects. The typed-data backbone underneath every other Conduction app, and the install you reach for first.
The typed-data foundation.
Define a schema once. The app gives you an API, a UI, validation, an audit log, and a citation-stable identifier per record. Every other Conduction app reads and writes through that one source of truth.
Schemas you write once.
Define a register's shape in JSON Schema. The app generates the API, validates every write, and exposes the data to other apps that speak REST.
One backbone, every app.
Every typed object lives in one register. Other apps consume it through the same API. No syncs to maintain, no duplicate sources of truth.
REST and GraphQL, auto-generated.
Both APIs roll out of the schema. No controllers to write, no spec to update when the schema changes, no glue code between OpenRegister and the apps that consume it.
Audit log, signed and timestamped.
Every read, write, and schema change leaves a tamper-evident trail. WOO and BIO compliance evidence ships with the install, no spreadsheet exports at audit time.
Citation-stable identifiers.
Every record gets a permanent identifier the moment you create it. Department reorganisations, system migrations, and renames don't break links to your data.
Open, forever.
Issues land in public, releases are tagged, and every register you create is exportable to plain JSON. The day you uninstall is as easy as the day you installed.
Partners shipping OpenRegister
Implementation, hosting, and integration partners that deliver OpenRegister to their customers. Pick the partner you already work with, or one whose stack matches yours.
Ship Conduction to your customers.
Three tiers: Host (ship our apps), Service (SLA + third-line support), Certified (trained, joint roadmap, tender-eligible). The apps stay open source, the relationship stays direct.
Apply through Support →Schema-first, ingest-anywhere, visualised by default.
Scroll the cards. Each pins as you reach it; the next slides up to cover.
Typed registers from a JSON Schema.
Define a schema, get a register. REST and GraphQL endpoints generate themselves, audit logging is on by default, citation-stable IDs land on every row.
See OpenRegisterOpenConnector fills the registers for you.
Existing system speaks REST, SOAP, GraphQL, files? OpenConnector pulls it in, validates against the schema, and writes typed rows. No glue code, no nightly batch.
See OpenConnectorEvery register is a MyDash data source.
MyDash reads the schemas directly. Drop a chart on a board, point it at a register, and the columns are typed. No BI database, no separate login.
See MyDashOn every Nextcloud dashboard.
Install OpenRegister and the home screen surfaces what changed in your data, what people search for, and what slipped through validation.
Recent records
Latest objects across every register the user has access to. Schema avatar, snippet, audit-stamp.
Schema activity
Sparkline of objects-created per schema this week. Click through to a register-by-register breakdown.
Top searches
What your team is looking for. Common queries with hit counts; surfaces gaps in the catalogue.
Apps that truly work together.
OpenRegister is what turns an office suite into a workspace. Every Nextcloud app on the install can read and write the same registers, and every register surfaces what lives in those apps. The integration runs on three levels at once: sidebar tabs that show linked records, dashboard widgets on every user's home screen, and a shared service layer that lets one app call another's data without anyone copy-pasting between tabs.
Every object in a register gets an auto-created folder. Drop files into it, write notes against the record, tag rows from the same workspace taxonomy your files use. Add a mail to a project and your colleagues see it without anyone forwarding. When someone shares one of those files in Nextcloud, the share is visible on the record. The case file is part of the workspace, not a parallel storage to keep in sync.
See the integration guideWhat OpenRegister adds to the workspace AI.
Install OpenRegister and the workspace chat gets three tools that cover the full register surface. The AI can read or write registers, schemas, and objects under the caller's own session, with every call validated against the schema and recorded in the signed audit log.
Manage registers
List, fetch, create, update, or delete registers. Registers group schemas and the objects written against them.
Manage schemas
List, fetch, create, update, or delete schemas. A schema is the JSON Schema that defines an object type inside a register.
Manage objects
List, fetch, create, update, or delete objects. Every write is validated against the schema and recorded in the signed audit log.
Three apps that compound the install.
OpenRegister is the data foundation. These apps consume it, surface it, and keep it filled.
The full spec, hover for detail.
Hover (or tab to) any feature to see the full description. Status hex shows where each one is on the maturity curve.