Veqsio
A self-hosted Jira alternative: your servers, your data
Veqsio installs on a clean Linux server with one command, keeps your issues and attachments in your own PostgreSQL, and upgrades with an automatic database backup.
Installing it
On a clean Ubuntu, Debian or RHEL-family server (x86_64 or arm64) with about 2 GB of RAM, 10 GB of disk and ports 80 and 443 open, the installer sets up Docker, generates secrets, runs the database migrations and configures HTTPS. Running it again upgrades the installation: the database is dumped first and your secrets are kept. For existing infrastructure there is a Docker Compose production stack with Nginx and Let’s Encrypt scripts.
What runs on your server
Bun and Hono for the API, Next.js for the web app, PostgreSQL for data and Redis for transient state. Nothing is sent to a vendor cloud, and the optional AI features are off by default and can use a self-hosted model.
Control you keep
| Topic | How Veqsio handles it |
|---|---|
| Data location | Your PostgreSQL and your attachment storage, on your servers. |
| Backups | Daily backup scripts with rotation, a restore-verification script, and a configuration health page that shows the last backup and last verified restore. |
| Upgrades | Versioned database migrations, a startup schema guard and an automatic dump before each upgrade. |
| Sign-in | Local accounts with a password policy and lockout, Microsoft sign-in, OpenID Connect; SAML, LDAP and SCIM with a licence. |
| Audit | An audit log of administrative changes with filters and CSV export. |
| Monitoring | /health and /ready probes, a token-protected Prometheus /metrics endpoint, structured JSON logs with request ids. |
| Scaling | Multi-node operation with advisory-locked background jobs. |
| Security | Deny-by-default authorization, input validation, rate limits, upload content checks, security headers and a published threat model. |
| Licence | AGPL-3.0 community edition; Enterprise modules use offline licence keys, and your data stays readable if a licence ends. |
Operating it day to day
The operations chapter covers instance settings, feature switches, backups, the audit log and configuration as code. The SSO and SCIM chapter covers identity.
Frequently asked questions
What do I need to run Veqsio?
A Linux server (x86_64 or arm64) with Docker, about 2 GB of RAM, 10 GB of disk and ports 80 and 443. The installer handles the rest.
How do upgrades work?
Run the installer again. It dumps the database to a backups folder first, keeps your secrets, applies versioned migrations and restarts the services.
Is there a hosted version?
Veqsio Cloud is coming soon. You can join the waitlist from the pricing section of the home page.
Does it need an internet connection?
Day-to-day use does not depend on a vendor cloud. Optional integrations such as Slack, Git hosting or an external AI provider need to reach those services; a self-hosted model keeps AI local.
Can I connect single sign-on?
Yes. Microsoft sign-in and OpenID Connect are supported, and SAML, LDAP and SCIM provisioning are available with a licence.
See it for yourself
The demo is open to everyone — no signup, no setup.