Shared Compute - General Compute
$12.49/mo
2 vCPU · 4 GB · 40 GB
Choose location
Phoenix, United States
| Provider | Plan | vCPU | RAM | Disk | Regions | Billing | Price |
|---|---|---|---|---|---|---|---|
| Virtualized | Shared Compute - General Compute | 2 | 4 GB | 40 GB | Phoenix, United States | Fixed price | $12.49/mo |
| Virtualized | Shared Compute - General Compute | 3 | 6 GB | 60 GB | Phoenix, United States | Fixed price | $17.49/mo |
| Virtualized | Shared Compute - General Compute | 4 | 8 GB | 80 GB | Phoenix, United States | Fixed price | $22.99/mo |
| Virtualized | Shared Compute - General Compute | 8 | 16 GB | 160 GB | Phoenix, United States | Fixed price | $44.99/mo |
| Virtualized | Shared Compute - General Compute | 16 | 32 GB | 320 GB | Phoenix, United States | Fixed price | $79.99/mo |
| Virtualized | Shared Compute - General Compute | 32 | 64 GB | 640 GB | Phoenix, United States | Fixed price | $139.99/mo |
Zammad Instant App
Zammad is an open-source helpdesk for email, chat and ticket queues. Compare live VPS prices, CPU, RAM, disk and regions, launch with a prepared admin login on the plan you choose, and keep root access.
Zammad
Instant App on marketplace VPS
Live marketplace offers
Choose billing and size, compare providers side by side, pick a location, then launch.
1 provider
Zammad is a self-hosted helpdesk for email and ticket queues. Use it instead of paying for Zendesk. Sign in as admin after boot, open tickets, invite agents and connect channels. No Instant App form fields are required at create time.

Open Zammad and sign in with the prepared admin account. The overview shows open work and agent tools.

Create tickets, assign agents and follow status. Keep support volume on hardware you control.

Invite agents, set roles and organize groups so the desk matches how your team works.

Tune branding, notifications and channels from the admin UI after the first login.
Compare live Zammad VPS plans from independent providers, then self-host a full helpdesk on the offer you pick. Use it instead of paying for Zendesk.
See live prices, regions and plan sizes before you buy. Shop helpdesk hosts across independent providers, including 4 GB boxes that fit Zammad well.
Pick a plan and Zammad is prepared on that VPS for you, including the admin account. You still get root access.
Compatible offers list cities and countries. Keep latency low for agents or keep ticket data in a place that matches policy.
Tickets, users and channels live on your VPS volume. You control SSH, DNS and who can open the helpdesk.
Most Zammad VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted helpdesk offers by price, size and region, then launch on the one that fits.
Zammad Instant App prepares Zammad on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.
Compare plans, pick a provider offer, and launch Zammad on that server.
01
Browse live offers below. A 4 GB plan is a solid start for Zammad without Elasticsearch. Sort by provider, size, price and region.
02
Choose the provider plan and region. There are no Instant App form fields to fill for Zammad.
03
Confirm checkout and wait for the server. Then open http://YOUR_IP/ and sign in with zammad_admin_email and zammad_admin_pass from your server notes. You keep root SSH.
NodeRings Instant App brings Zammad up with the official Docker Compose stack and creates the admin account with AutoWizard. Use the sections below to reach the UI, find passwords, and operate the stack.
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_passwordCompose project directory
/opt/noderings/zammad
/opt/noderings/zammad/docker-compose.yml
/opt/noderings/zammad/.envOfficial compose project, stack file, and generated secrets.
Credentials file
/root/.noderings_passwordWritten once on first boot.
Boot unit
/etc/systemd/system/noderings-zammad.serviceBrings compose up after Docker is ready.
Install log
/tmp/zammad-admin.logCompose and AutoWizard output.
Compose runs Zammad (nginx, rails, websocket, scheduler), Postgres, Redis and Memcached. Elasticsearch is disabled in this Instant App. The UI is on HTTP port 80.
zammad-nginxHTTP front end on port 80.
zammad-railsserverZammad application server.
zammad-postgresqlPostgres for tickets and users (not published on the host).
zammad-redis / zammad-memcachedCache and session helpers.
Container status
cd /opt/noderings/zammad && docker compose psLive logs
cd /opt/noderings/zammad && docker compose logs -fRestart containers
cd /opt/noderings/zammad && docker compose restartLogin page probe
curl -sS -o /dev/null -w '%{http_code}\n' http://127.0.0.1/systemd unit status
systemctl status noderings-zammadYour Zammad app starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.
Add your domain
Sign up at Cloudflare and add the domain you want to use.
Point it at your VPS
Create an A record to your server IP and leave the orange cloud on.
Open the https site
Visit https://your-domain and sign in with the admin credentials from your server notes.
Only allow Cloudflare
Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:
curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; doneKeep port 22 allowed for SSH. Prefer a real hostname in Zammad settings after DNS is ready.
Zammad runs as a multi-container Docker stack with Postgres, Redis and Memcached. This Instant App disables Elasticsearch to fit a 4 GB starting point. Busier desks need more RAM. These are starting points, not guarantees.
| Workload | Illustrative starting point | Note |
|---|---|---|
| Small team helpdesk (no Elasticsearch) | 2 vCPU / 4 GB RAM / 40+ GB disk | Suggested Instant App floor for Zammad with Elasticsearch disabled. |
| Many agents and channels | 2–4 vCPU / 6–8 GB RAM | More headroom when agents stay signed in and email volume grows. |
| Full-text search with Elasticsearch | Add about 4 GB RAM for ES on the same box | Enable Elasticsearch later if you need richer search. Official docs recommend more RAM with ES. |
| Ticket history and attachments | Disk sized to history and uploads | Postgres and storage volumes grow on the VPS. Keep backups off-box. |
These are starting points, not guarantees. Needs depend on ticket volume and agent count.
This is self-hosted Zammad on a provider VPS, not managed Zendesk. You pick the plan. Zammad is prepared on that server. Day-to-day care stays with you.
Zammad is prepared on the VPS with no Instant App form variables. AutoWizard creates the admin account so the open first-setup page is closed. Marketplace listing covers compatible Compute Instance plans and create-flow credentials for root SSH.
Root SSH on the VPS. You own tickets, agents, channels, DNS, TLS, OS updates and backups unless a provider product says otherwise.
Managed SMTP, automatic TLS, hosted Elasticsearch and support SLAs are not bundled in. Finish TLS and mail after the server is up if you need them.
NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after Zammad on the server is yours.
Zammad is a free, open-source helpdesk. Teams use it for email and ticket queues on hardware they control.
No. Zammad Instant App asks for no form variables at create time. After the VPS is ready, sign in with the admin email and password from your server notes.
No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, Zammad is prepared on that provider server, and you manage tickets from there.
No. You get a virtual machine with Zammad prepared for you, plus root access. That is different from a managed product that owns updates and support for you.
It prepares Zammad on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.
Open http://YOUR_IP/ and sign in with zammad_admin_email and zammad_admin_pass from /root/.noderings_password.
This Instant App disables Elasticsearch so a 4 GB plan can run. You can enable Elasticsearch later if you need full-text search and have more RAM.
A common starting point is about 2 vCPU, 4 GB RAM and 40 GB disk without Elasticsearch. Busier desks usually need more RAM. Use the sizing guide above and compare plans in the list.
You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the admin credentials from your server notes.
Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and compliance needs.