Roles, members, and access rules in the running self-hosted web app
In everyday use
What you can do with it
Self-hosting moves control and responsibility to the operator. Open Inventory provides Compose files, migrations, a health endpoint, PostgreSQL and persistent upload storage as a documented base. Backups, restore tests, TLS, network exposure and updates remain operational tasks.
Run and inspect the web app, API and iOS client on infrastructure you control
Define roles, granular permissions and content-dependent access rules
Manage the database, files, secrets, backups and optional providers explicitly
Features in detail
Operations and security
Roles and conditional rules
Manage local accounts, custom roles, granular permissions and content-dependent access rules. Auth0 or a standards-based OpenID Connect provider can be added for sign-in.
Docker Compose and PostgreSQL
Containers, migrations, a health endpoint and persistent volumes for PostgreSQL and local uploads are checked in. Configuration and secrets remain deployment concerns.
Selectable file storage
Store uploads in a persistent local volume by default or configure Openinary. Database and file storage must be backed up as one recoverable dataset.
Multiple organizations
Separate workspaces, data, and memberships within one deployment. Roles and permissions are evaluated in the currently selected organization.
AI usage and monthly limit
Review estimated cost by action, provider, and status. An organization limit is checked before every paid AI call and can stop paid AI completely.
Controlled offline copies
Keep selected views available offline on a trusted device. Disabling offline access or signing out removes the locally stored copies.
MIT-licensed source
The web app, API and native iOS client are published in one repository. The MIT license permits inspection, modification, operation and redistribution.
Step by step
An open stack still requires operating decisions
Starting Compose is the first step. Identity, persistence, recovery and controlled upgrades are required for a durable service.
01
Start the instance
Use the checked-in Docker Compose services, PostgreSQL, migrations and health endpoint as the baseline.
02
Restrict access
Configure accounts, roles and rules, then decide whether the instance is private or exposed through a hardened reverse proxy.
03
Back up all persistent data
Back up PostgreSQL and the selected file store together, and verify restoration regularly.
04
Apply updates deliberately
Review repository changes, update images and migrations in a controlled sequence, and monitor the health endpoint.
Native iOS app · German demo data
On site, too
The iOS client connects to the operator's instance.
The native SwiftUI app is built from the same repository and uses a configured server origin. Reachability, TLS and certificate validity are therefore part of the deployment model.
Configure the server origin for the target instance
Inspect web, API and iOS code in one repository
Use HTTPS for connections outside a trusted local network
