Skip to the content
OpsCommand
Norsk Book a demo
Menu

Security and control

Governance, built in. Your data stays yours.

Your organisation’s records stay yours: kept apart from every other organisation, changed only by the people you allow, and recorded in a log that shows if anything was altered.

Book a demoFound a vulnerability?

Four promises

Each one kept in the product itself.

  1. 01

    Isolated organisations

    Each organisation’s data is kept apart from every other’s, and that separation is tested on every change.

    How it is keptEvery table enforces row-level security in the database itself, tested on every change: one organisation never reads another’s records.

    Tested on every change

  2. 02

    Tamper-evident audit

    Every change is recorded in a log that shows if anything was altered. Verify it and export it when you need to.

    How it is keptEvery change is recorded in a hash-chained audit log that can be verified, and exported with the organisation’s data.

    Verify and export

  3. 03

    Your identity provider

    Entra ID, Google, Okta, SAML and SCIM; two-step sign-in by role.

    How it is keptPeople sign in through your own identity provider, so joiners and leavers follow your directory; what each person may do is set by role.

    SAML · SCIM · two-step

  4. 04

    Your infrastructure, if you want it

    Run OpsCommand on your own servers with an offline licence when your policies require it.

    How it is keptDocker Compose or Kubernetes, with your identity provider, database and backups, an offline licence and signed update media; nothing is sent to OpsCommand.

    Offline licence

Permissions

Every role, exactly what it may do.

Roles are granted to a person for the whole organisation, a department, a team or one service. Sign-in never grants a role by itself.

Every role,
Run the accountLeadership viewServicesMonitorsWork incidentsVerify and closeCustomer reportsCode workStatus pageAudit
Organisation administratorTwo-step sign-in required
Executive management
IT operations directorTwo-step sign-in required
IT administratorTwo-step sign-in required
Customer support
System administratorTwo-step sign-in required
Software developer
Service owner
Managed operations (Assisted)Two-step sign-in required

Everyone with a role can read what their role covers. A member from an outside provider can never hold a role that runs the account.

And underneath

The rest of how it is kept safe.

  • Secrets stay sealed

    Integration secrets are sealed with the installation’s own keys; messages and logs are redacted before they are stored.

  • AI is off by default

    An organisation chooses whether to use AI. It decides nothing; every output is labelled, sourced and logged.

  • Your data is yours

    Export everything at any time in open formats with a verifier that needs only Node; leave, and it is erased.

  • Supply chain

    Release images are signed, with provenance and an SBOM. Report a vulnerability to security@opscommand.dev: we acknowledge within two working days and disclose in coordination with you.

  • Independent of FlyttGo

    OpsCommand is a product of its own. Its code, data and infrastructure are separate, and a drill proves it can be moved without FlyttGo’s systems.

At a glance

Hosting
Our cloud, or your own servers with an offline licence and signed updates
Identity
Entra ID, Google and Okta; SAML and SCIM; two-step sign-in by role
Data
Each organisation isolated; a tamper-evident audit log; full export of your data
Monitoring
Website and API checks from outside, health endpoints, heartbeats, journey monitors, OpenTelemetry and an events API
Integrations
GitHub, GitLab, Jira, Slack, Microsoft Teams and signed webhooks
Customers
A report-a-problem widget, private tracking links and status pages on your own domain
AI
Off until you turn it on; every suggestion cites its evidence, and a person decides
Languages
English and Norwegian

Found a vulnerability?

Write to us. We acknowledge within two working days and disclose in coordination with you.

security@opscommand.dev

See OpsCommand on your own services.

A 45-minute walkthrough with the people who run your services: one incident, from first alert to verified fix.