Licensed edition

Octoprox Enterprise

Everything in Octoprox, plus a record of who got in: every sign-in and API token in the audit log, across the whole install, ready for your SIEM.

Get in touch Read the audit log docs
Planned Your own identity provider, group sync and SCIM provisioning
  • Built on the public release Its own image, self-hosted in place of the public one, on the same database.
  • Seats and 30 days' grace Seats count active users. A grace period of 30 days follows the expiry date.
  • Nobody is ever locked out The license decides only what the audit log records and whether the Activity page can be read.
The Activity page under Administration: sign-ins, API token events and changes across every project, newest first, with one change open beside the list The Activity page under Administration: sign-ins, API token events and changes across every project, newest first, with one change open beside the list

Administration → Activity, with demo data.

Available today

Who got in, as well as what changed

Every edition records each change a person makes, with who made it, when and the fields it changed. Enterprise adds four things.

  1. Sign-ins

    Every sign-in by password, invite link or sign-in provider, failed ones included, with its method, the address it came from and the browser. A failed sign-in records why it was refused.

  2. API tokens

    Each personal access token issued, used for the first time and revoked, and each sign-in provider account unlinked from a user.

  3. The Activity page

    Every entry of the install on one page under Administration → Activity, the changes recorded before the license included, filtered by entity type, action, the user who acted, project and time.

  4. Export for a SIEM

    Every entry under the page's filters as JSON lines, and an audit line per entry in the server log for a log pipeline to collect.

Details in the audit log docs
The Activity page: the Export JSON lines button, the retention setting, filters by entity, action, actor, project and time, and the list of entries with Signed in, Token first used, Token issued and Sign-in failed among the changes The Activity page: the Export JSON lines button, the retention setting, filters by entity, action, actor, project and time, and the list of entries with Signed in, Token first used, Token issued and Sign-in failed among the changes
The Activity page, with demo data. The numbers match the list.
Deployment

Same Octoprox, one image swap

Octoprox Enterprise is the public release with the Enterprise package added, published as its own image. Everything else works as it does on the free edition.

docker-compose.ghcr.yml 1 line changed
 services:   octoprox:-    image: ghcr.io/octoprox/octoprox:latest+    image: ghcr.io/octoprox/octoprox-enterprise:6.8.2
  1. Run the Enterprise image

    In place of the public one. Each Enterprise release follows the public release of the same version.

  2. Keep your settings and database

    The same settings and roles, on the same database.

  3. Paste the license key

    On the License card under Administration → System, to turn on what Enterprise adds.

How licensing works

Licensing, plainly

One key turns on what Enterprise adds. Renewing, or adding seats, is a new key pasted over the old one.

Seats
Seats count active users. More active users than seats blocks nobody: admins see a banner.
A license key
oxl1.

It names

  • Organisation
  • Seats
  • Expiry date
  • Features

The License card under Administration → System shows them, with the seats in use.

Expiry, grace and after

Active up to and including the expiry date, then 30 days' grace. In every state, the license decides only what the audit log records and whether the Activity page can be read.

What is recorded and readable in each state of a license
Active Until expiry Grace period 30 days After grace Until a new key
Sign-in, passwords and tokens Work the same in every state: nobody is ever locked out
Changes, with who, when and the fields Recorded, as on every edition
Sign-ins, token events and audit lines in the server log Recorded Not recorded
The Activity page and its export Readable, so an install can still answer an auditor
Planned

Access from your directory

Later releases are planned to hand access control to your directory. None of these is available yet; Single Sign-On describes each as designed.

  • Planned Domain rules: everyone whose verified email is at your domain signs in and gets a user on first login, with a default role.

  • Planned Your own identity provider: any OpenID Connect or SAML 2.0 provider, such as Okta, Entra ID, Auth0, Keycloak or Ping.

  • Planned Group sync: roles from directory groups, re-evaluated on every sign-in.

  • Planned Enforcement: the identity provider required for everyone except break-glass admins.

  • Planned Provisioning: SCIM 2.0, so a leaver loses access the moment the directory says so.

Available today On every edition: sign-in with a password or a Google, Microsoft (one Entra tenant) or GitHub account, and personal access tokens.

Editions

Free and Enterprise

The same release on both. Enterprise adds a record of who got in, across the whole install.

Free and Enterprise compared
FeatureFreeEnterprise
Proxy routing, providers, IP attribution, tunnel devices, metrics and the dashboard Yes Yes, the same release
Sign-in with a password or a Google, Microsoft or GitHub account, and personal access tokens Yes Yes
Every change a person makes, with who, when and the fields it changed Yes Yes
Sign-ins, failed ones included, with method, address and browser No Yes
API tokens issued, first used and revoked No Yes
The whole install's audit log on the Activity page, with filters No Yes
Export as JSON lines, and an audit line per entry in the server log No Yes
Domain rules, your own identity provider, group sync, enforcement and provisioning No Planned
Get started Get in touch
Talk to us

Get Octoprox Enterprise

Licenses are arranged by email: write to us for one, or with any question.

Get in touch
A license comes with
  • The license key It names your organisation, seats, expiry date and features.
  • Access to the image For the GitHub accounts you name, from GitHub's container registry.
  • What it turns on Sign-ins, API tokens, the Activity page and export for a SIEM.