Vikunja 2.7.1 (AGPL-3.0) with PostgreSQL 17 on Ubuntu 24.04, with HTTPS, registration closed and a generated account created before the site is published. Vikunja's paid licence features are not included.
This AMI runs Vikunja, the open-source task and project manager, with PostgreSQL 17 on Ubuntu 24.04 LTS. The official Vikunja image (vikunja/vikunja) is pinned to 2.7.1, with PostgreSQL 17.11, and baked into the AMI, so first start does not depend on a registry. Vikunja is an independent open-source project and Perimattic is not affiliated with it; product names are trademarks of their respective owners.
Why Vikunja?
Vikunja manages tasks and projects with lists, Kanban boards, Gantt and table views, labels, priorities, due dates, reminders, attachments, saved filters, teams, sharing and a REST API with CalDAV support. It is a single, light application.
What Perimattic adds
Account created for you, registration closed: a fresh Vikunja lets anyone register. During first-login setup this AMI creates your account with Vikunja's own command line (your admin email, the user name admin and a random 24-character password generated on your server), and Vikunja runs with registration disabled from its first start, so nobody else can sign up. Setup then checks that the password works, that a wrong password is refused, that registration is refused and that the API refuses anonymous requests. The token-signing secret and the database password are generated per instance; there are no default or shared credentials in the image.
HTTPS: Apache is configured as a reverse proxy and a free Let's Encrypt certificate is requested for your domain with certbot. Vikunja's public URL is set to your domain, it listens only on the loopback interface and PostgreSQL is reachable only inside the Docker network.
Patched base: Ubuntu 24.04 LTS built through an automated EC2 Image Builder pipeline, with security updates applied at build time.
What you should know
Paid features are not included. The Vikunja code in this image contains a licence system that unlocks four optional features for paying organisations: the in-app admin panel, user invitations, time tracking and audit logs. No licence key is supplied or bypassed, so those features are off. Because user invitations are one of them, and registration is closed, additional users are created on the server with a Vikunja command (shown in the access notes), or through your own OpenID Connect provider if you configure one.
Link shares are public by design: a project you share by link is readable (or editable) by anyone with that link, without a login. You can switch link sharing off in the compose file. The API reports its version and feature flags at /api/v1/info without a login; everything else needs a token.
No mail server is configured, so Vikunja sends no reminders, password-reset or notification emails until you add your own SMTP settings (use port 587 or 465: Amazon EC2 blocks outbound port 25). Error reporting to Sentry is off by default.
Vikunja is light: about 40 to 90 MB of memory for the application and about 65 to 75 MB for PostgreSQL in our tests, so a t3.small (2 GB) is the recommended starting size.
Licence
Vikunja is released under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later); the desktop application folder in the repository is GPL-3.0-or-later and is not part of this image. This AMI runs the unmodified upstream image, whose source is at github.com/go-vikunja/vikunja. PostgreSQL is released under the PostgreSQL License.
Getting Started
Launch the AMI and open ports 22, 80 and 443 in the security group
SSH in and answer the setup prompts (domain and admin email)
Open https://your-domain and sign in as admin with the password printed at the end of setup
Create projects and tasks; add users with the command in /opt/app/access.txt
A domain name with an A record pointing at the instance is required, because the site is served over HTTPS.
Support
Managed and supported by Perimattic, a cloud infrastructure company with 13+ years of experience serving global clients. We offer free setup assistance, custom integrations, infrastructure consulting, and 24/7 support.
Highlights
Vikunja 2.7.1 (AGPL-3.0) with PostgreSQL 17.11, pinned and pre-installed: self-hosted tasks, boards and projects. Vikunja's paid licence features are not included.
Secure first login: your account is created with a random 24-character password before the site is published and registration is closed; anonymous API requests refused; HTTPS through Apache and Let's Encrypt.
Built on patched Ubuntu 24.04 LTS and supported by Perimattic: free setup assistance at aws-support@perimattic.com.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
If you are an AWS Free Tier customer with a free plan, you are eligible to subscribe to this offer. You can use free credits to cover the cost of eligible AWS infrastructure. See AWS Free Tier for more details. If you created an AWS account before July 15th, 2025, and qualify for the Legacy AWS Free Tier, Amazon EC2 charges for Micro instances are free for up to 750 hours per month. See Legacy AWS Free Tier for more details.
You pay by the hour for a managed Vikunja task and project manager running on an EC2 instance you choose. Pricing is not tiered by features; every option delivers the same managed service. Instead, the dimensions map to AWS EC2 instance types across families such as compute-optimized (c), general-purpose (m, t), memory-optimized (r, x, z), storage-optimized (d, i), and accelerated computing (g, p, inf, trn). Within each family, larger sizes carry more CPU, memory, and resources and cost more per hour. Pick the instance size that matches your workload; billing accrues hourly based on usage.
Top-of-mind questions for buyers
Am I charged when my chosen EC2 instance is stopped or powered off?
The hourly software fee meters running time only. A fully stopped instance stops accruing the hourly software charge. Underlying AWS storage and other resource fees may still apply while the instance is stopped, but the Vikunja software charge tracks active hours.
What do I actually receive for the hourly fee on each instance size?
You get a dedicated, managed Vikunja instance on the EC2 size you pick. Perimattic handles provisioning, TLS certificates, daily backups, managed upgrades, and security patching. Larger sizes add CPU and memory for heavier workloads; the managed service stays the same across all sizes.
Does my bill change automatically if I need more capacity?
No automatic tier jump occurs. Each instance size bills at its own hourly rate while running. To get more CPU or memory, you choose a larger instance size, which then meters at that size's hourly rate. Switching sizes is a manual choice, not an automatic upgrade.
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Initial release.
Application: Vikunja 2.7.1 (container image pinned, baked into the AMI).
Base: Ubuntu 24.04 LTS, fully patched at build time, built by an automated EC2 Image Builder pipeline.
TLS: Apache reverse proxy with a Let's Encrypt certificate requested by certbot at first login.
Credentials are generated on the instance at first login; none are present in the image.
A random password is generated at first login and used by Vikunja's own 'user create' command to create the account before the site is published; registration is disabled from the first start; setup verifies that the password works, that a wrong password and registration are refused and that anonymous API requests are refused.
Application: Vikunja 2.7.1 (AGPL-3.0-or-later, unmodified official image vikunja/vikunja) with PostgreSQL 17.11 (both pinned). Vikunja's paid licence features (admin panel, user invitations, time tracking, audit logs) are not included.
No SMTP is configured: Vikunja sends no emails until the buyer adds a mail server. Link shares are public by design.
Database: reachable only inside the Docker network.
Additional details
Usage instructions
Launch an Instance
From AWS Marketplace, click Continue to Subscribe and then Continue to Configuration to launch the AMI.
Choose the Recommended Instance Type
t3.small (2 GB of memory) is the recommended starting size: Vikunja used about 40 to 90 MB and PostgreSQL about 65 to 75 MB in our tests. Vikunja's paid licence features (admin panel, user invitations, time tracking, audit logs) are not included.
Configure Security Group
Allow inbound traffic on the following ports:
22 (SSH) - terminal access for setup
80 (HTTP) - needed to validate your domain for the TLS certificate
443 (HTTPS) - access to Vikunja
Point a domain at the instance
Create a DNS A record (for example tasks.example.com) pointing to the instance's public IP before you log in.
Connect to the Instance
ssh -i <your-key.pem> ubuntu@<public-ip>
First-Login Setup
The first SSH login runs a guided setup:
Prompts for your domain and admin email and checks the DNS A record
Generates a random 24-character password, a database password and the token-signing secret on your server
Starts PostgreSQL and Vikunja (registration is closed from the first start) and creates your account with Vikunja's own command
Checks that the password works, that a wrong password and registration are refused and that anonymous API requests are refused
Configures Apache as an HTTPS reverse proxy and requests a Let's Encrypt certificate
Prints the URL and the credentials; they are also stored in /opt/app/access.txt (root only)
If a step fails, fix the problem shown and log in again: the setup resumes where it stopped.
Access Vikunja
Open https://<your-domain> and sign in as admin with the generated password (view it again
with: sudo cat /opt/app/access.txt). Add users with the command shown in that file.
Credentials
Generated on your server, never shared between customers. View them again with:
sudo cat /opt/app/access.txt
Manage the Services
cd /opt/app
sudo docker compose ps
sudo docker compose restart
Tasks and projects are in the PostgreSQL database in /opt/app/postgres and attachments in /opt/app/files: back up all of /opt/app or snapshot the volume before upgrades. Registration is closed: add users on the server with the vikunja user create command in /opt/app/access.txt. The admin panel, user invitations, time tracking and audit logs are paid Vikunja licence features and are not included. Link shares are public by design. The Vikunja container may restart once during the first start (seen once in testing, cause unknown).
Thank you for subscribing.
Need Support or Customization?
Perimattic's team can help with setup issues, custom features and integrations:
What We Help With:
Initial setup and configuration assistance (free)
Troubleshooting connectivity, performance, and backup issues
Custom development and integrations
Infrastructure consulting and architecture review
Migration planning from other solutions
Automation solutions and scaling guidance
Instance Sizing Guidance:
t2.medium or t3.medium: Development environments, small applications
m5.large: Production workloads with moderate traffic
m5.xlarge: High-traffic production deployments and larger datasets
For workload-specific sizing recommendations, contact our team for a free consultation.
Refunds and Issues:
If you experience any issues or need to request a refund, contact us at aws-support@perimattic.com and we will respond promptly.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Reverse proxy manager 2.16.0 (MIT) on Ubuntu 24.04 with a web interface: proxy hosts, redirections and streams on ports 8080 and 8443, the interface behind HTTPS with an administrator created for you.
Self-hosted time tracking and timesheet application 2.71.0 (AGPL-3.0) with MariaDB 11.8 on Ubuntu 24.04: customers, projects, invoices, reports, HTTPS, a generated administrator and no self-registration.
Self-hosted project and task management 3.13.2 (AGPL-3.0) with MariaDB 11.8 on Ubuntu 24.04: HTTPS, installation completed for you with a generated owner password, no sign-up page.
Self-hosted work package and project planning 17.9.6 (GPL-3.0) with PostgreSQL on Ubuntu 24.04: HTTPS, the first-run setup completed for you with a generated administrator, no sign-up page.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.