Orbelle for the whole organisation, installed on your own Windows Server, Red Hat Enterprise Linux or container platform. Users work in the browser or the desktop app, and project data never leaves your network.
Users open Orbelle at an address on your network, such as https://orbelle.agency.internal, and sign in. Nothing to install on their computers, and their working copy is kept on the server, not on the computer they used.
Users who prefer the desktop app connect it through the server instead of straight to a database. It keeps its own copy, carries on when the network drops, and signs in with the same account and MFA code.
A separate set of pages at /admin, for administrators only. Licence and seats, users and roles, sign-in, the shared register, backups, network, updates and the audit log, without anyone signing in to the server itself.
Only the server connects to the database, so users don’t need database accounts and the database can be firewalled to the server alone.
Select a page in the console’s menu on the left to see it.
The dashboard shows the service, database, directory and integrations at a glance, with seats used against the licence, the last leaver check, anything that needs attention and recent admin activity.
The same registers, dashboards and reports as the desktop app, with the controls administrators expect from a server.
Orbelle accounts made in the admin console, Active Directory, or both. With AD, roles come from your groups, and leavers are found by a daily check and their seats released. The server’s own AD account can be set up so that no password is stored.
Codes from an authenticator app such as Microsoft Authenticator, set up by scanning a QR code, with one-time recovery codes. Administrators choose: off, optional, required for admins, or required for everyone.
Keep the shared register in your own PostgreSQL database or in SharePoint lists. Use one, or keep the other up to date as a copy. In the database, every change is recorded under the user who made it, and deletion limits apply to each user.
Licensed by the number of users. Each user takes one seat however many computers they use. A short grace period covers a temporary increase, and a released seat becomes free after 30 days.
Scheduled every few hours, daily or weekly, with retention by count and age. Backups are encrypted with a passphrase, saved only to locations administrators approve, and can be checked and restored from the console. A backup missed while the server was off runs when it’s back, and a restore is all or nothing.
New app features install from the admin console, online or from a signed file, without reinstalling the server. Each update is signature-checked, and the previous version can be restored.
Set the server’s address, the name users open Orbelle at. Then choose which of the server’s addresses Orbelle serves on, who can connect to each, whether the admin console is offered there, and the DNS names it answers to. The server’s own network settings are never changed.
The organisation’s Forecast key is kept encrypted on the server, and projects are synced on a schedule. Clarity, Jira Cloud and Jira Data Center work as they do in the desktop app, read-only, and only to the sites the console allows. Each integration can be turned off in the console.
Sign-ins, admin actions, licence changes and backups are recorded. The log can’t be edited, and a change made outside Orbelle is flagged.
Orbelle Server needs nothing else to start: its own records are built in. The shared register, Active Directory and integrations are added from the admin console when you’re ready.
A Windows service that never runs as an administrator. The install script locks the data folder down to the service.
A systemd service under its own unprivileged user, with sandboxing turned on. It also runs on RHEL rebuilds such as Rocky Linux and AlmaLinux.
An image for Podman, Docker, Kubernetes and OpenShift, based on Red Hat UBI. It runs as a non-root user with a read-only file system, and suits OpenShift’s restricted policy. Supplied as a file for sites with no registry access.
A server or container platform, a TLS certificate for the address users connect to, and a licence key. Optionally, a PostgreSQL database, an Active Directory service account and a SharePoint site.
Every package comes with checksums, and the container package is signed so it can be checked offline before it’s loaded. A software bill of materials comes with every build.
No configuration files to edit. A setup page on the server asks for the address, the certificate (or makes a temporary one to get started) and who may open the admin console, and checks them before saving. The same one-time setup code then opens the admin console: choose how users sign in, make the first administrator, install the licence, and finish.
A Server licence is tied to one installation and sized by the number of users, in the browser or the desktop app. Email info@orbelle.net with the request code from the admin console for a quote.
| Users | Seats |
|---|---|
| Up to 10 users | 10 |
| 11 to 25 users | 25 |
| 26 to 50 users | 50 |
| 51 to 100 users | 100 |
| 101 to 250 users | 250 |
| More than 250 users | Priced individually |
Going over the limit doesn’t lock anyone out: up to 10% more users can sign in for 10 days while a larger licence is arranged. When a licence ends, Orbelle becomes read-only and everything can still be viewed and exported. See the security overview for how the server protects itself.
