15 concurrent members
HTTP p95 301 ms at 500 items, 494 ms at 5,000. Same mix, zero failed requests.
Full control of work data
Run Takt where you decide
takta.app is only this website. The product runs in infrastructure you choose, with a PostgreSQL database you own.
A customer install, not a Takt cloud
A Docker Compose stack starts Takt and Postgres — online from
Docker Hub, or airgapped with docker load.
You set the secret, open the app, create the first account and
complete the setup wizard. Scale from a laptop trial to your
own servers.
- No mandatory Takt-hosted SaaS environment
- Your PostgreSQL, your backups, your retention rules
- Email and password, Microsoft Entra ID sign-in, authenticator MFA
- Backups every 30 minutes and a live status page, inside the product
- CLI and MCP for the terminal and agents, without giving Takt your git host
Demo — not for production. This public install is for trying Takt. Do not run it as a production system yet. For a demo AI key, e-mail takt@fennister.com.
Measured with k6, not a promise
One organisation, 15 members, CLI API, AI off, one Node process on a laptop. 15 September 2026. Occupancy uses 8–12 s think-time (list, open, occasional create). Isolated list is 5 requests/s for 30 s.
500 to 5,000 items
Isolated list grows with org size. Open-one at 5,000: 34 ms. Search: 114 ms → 281 ms.
Create p95 at 3/s
New work item into one delivery, 500-item org. Comments ~47 ms. Not a browser or board measurement.
A ramp toward 40 list requests/s saturates the database pool (p95 ~7.5 s) — that is not the 15-person case. Not measured: the web UI, AI, file storage, two app replicas, 20,000 items.
NIS2-oriented controls in the product
Takt is not NIS2 certified. Cybersäkerhetslag (2025:1506) and MCFFS 2026:11 (from 1 October 2026) apply to the organisation that runs the instance. The product ships the controls below; the operator still owns TLS, off-site copies, training and incident reports to the authority.
Lockout after failed logins
Password min 8, bcrypt cost 12. TOTP MFA; organisation admins can be required to enrol. Three roles.
Postgres dump cadence
Last 48 dumps kept (about 24 h). File-store tarballs on a cron you set. Restore is audited.
Org audit retention
Field names and ids, not bodies. Auth events on stdout. SBOM, image digest and checksums on every release.
Incident clocks for the operator
Early warning and notification under the Act. Start security updates within 72 h of a release. We acknowledge vulnerability reports within five business days.
Twelve product items in the NIS2 mapping are shipped (MFA, lockout, audit log, headers, backups, SBOM, admin MFA, file backup script, image digest). Scope, named roles and registration stay with the customer. Not in the product: SIEM, SAML, SCIM, WAF.
Keep your git host. Connect for traceability.
You keep GitHub, GitLab or Azure DevOps Server. A later connection (Coming) lets a work item point at the pull request and the code in the repo — from need to what actually changed. Takt is not a git server and there is no live sync today.
Who this is for
Public sector, regulated teams, and anyone who cannot put work data in someone else’s SaaS. Self-hosting opens the door. Daily use and the goal-to-work model have to win the rest.