Security and data

Etapero installs on your server, so project data stays in your infrastructure. Below is what the system does and what stays on your side.

No sign-up needed.

Your data stays with you

Etapero is one Docker image, and data is kept in your PostgreSQL database.
Only the public demo with made-up data runs in the cloud; the demo has no access to Jira.

Sign-in and sessions

In a corporate installation sign-in goes through Keycloak (OIDC) — your company’s single sign-on.
A user switched off in Etapero cannot sign in, even if they exist in Keycloak.
Where password sign-in is on, passwords are stored as scrypt hashes with a random salt.
The session token is stored in the database only as a hash; the session cookie is HttpOnly, Secure and SameSite=Lax.
Sign-in attempts are rate limited — both per address and per email.

Roles and access

Permissions are set per role; the system administrator has all of them.
Business units with their own administrators, and project access: view, edit, administer.
Projects are visible to every user of the system, and only those given access can change them.
The last active administrator cannot be switched off.

Audit log

The log records changes to projects, the work breakdown, issues, risks, decisions, users, roles, access, tokens, webhooks and calendars, plus sign-ins and sign-outs.
Field changes are recorded as “before → after”.
Work breakdown changes are logged in the same transaction: if the log entry fails, the change is not saved.
Log entries are kept with no time limit.

Read-only integrations

Every request to Jira is checked against an allow list: only sign-in, search and reads are permitted, everything else is blocked before it is sent.
GitLab — only reads of a branch, its commits and a commit’s merge requests, only over HTTPS and only to the configured address.

API and webhooks

An API token is shown once and stored as a hash; a token has permissions, an expiry date and a rate limit.
Webhooks are sent over HTTPS only; with a secret set, the body is signed with HMAC-SHA256.

Backups

Database backup scripts with a check of the copy and a checksum come included, along with restore and restore-drill scripts.
The administrator section shows the state of the latest backup.

What stays on your side

The network, server access and TLS certificates.
Updates of Etapero and PostgreSQL.
The backup schedule, keeping the copies and testing restores regularly.
The Jira account for the sync — read-only permissions are enough.
Access to the database itself: integration credentials are kept in system settings inside it.

Related articles

Jira and the project plan: dates above the tracker
Why Jira issues are not enough to manage project dates, how to link a plan to the tracker, and what a read-only sync gives you.
Self-hosted project management software: how to choose
A checklist for choosing self-hosted project management software: data, installation, sign-on, permissions, audit, integrations, planning, portfolio, import, support.

Try it yourself

The demo runs in your browser with no sign-up: you enter as a demo user and can edit the sample projects.