01 — Support ticketing, self-hosted

YOUR HELPDESK.INSIDE YOUR EC2.ZERO DEPENDENCIES.

A production-ready support ticket system delivered as an Amazon Machine Image. Deploy in one click, keep full root access, own every byte of your data.

0+
Instances deployed
0.9%
Uptime on EC2
0s
Avg. launch time
ScrollEC2 · AMI · v3.2
IT TEAMS
CUSTOMER SUPPORT
INTERNAL OPS
FULL ROOT ACCESS
1-CLICK DEPLOY
COMPLETELY PRIVATE
IT TEAMS
CUSTOMER SUPPORT
INTERNAL OPS
FULL ROOT ACCESS
1-CLICK DEPLOY
COMPLETELY PRIVATE
02 — Built for

One image. Three teams. Zero compromise.

The AMI ships pre-configured for the three groups that depend on ticketing most.

IT Teams
01

IT Teams

Total infrastructure control. Runs entirely inside your own EC2 instance with full root access, custom SSL, and no third-party data processors in the loop.

02

Customer Support

Sub-second ticket routing, SLA timers, canned replies and a shared inbox built for teams that live in the queue.

Internal Operations
03

Internal Operations

Military-grade data privacy. Every ticket, attachment and audit log stays within your VPC boundary — compliant by architecture, not by promise.

03 — Documentation

Docs written for engineers, not marketers.

GET STARTED

1-Click Deploy

Subscribe on Marketplace, pick your instance size, launch. SSH keys and endpoints ready in ~90 seconds.

CONFIG

Environment

Everything driven by a single .env — SMTP, domains, retention. No opaque control planes.

INTEGRATE

Webhooks & API

REST API + signed webhooks for Slack, PagerDuty and your own tooling.

OPERATE

Backups & Upgrades

Snapshot-friendly volumes and zero-downtime rolling upgrades baked in.

04 — Support Workflows

From inbound noise to closed ticket.

Every ticket flows through a predictable, auditable lifecycle. No black boxes — you can read the source of every automation running inside your instance.

$ curl -X POST https://helpdesk.internal/api/tickets \
-H "Authorization: Bearer $TOKEN" \
-d '{"subject":"Login failing","priority":"high"}'
→ 201 Created · #TK-4821 · assigned
01

Capture

Tickets arrive via email, web form or API and land in a unified queue with auto-assigned IDs.

02

Route

Rules engine tags priority, assigns owners and starts SLA timers the moment a ticket opens.

03

Resolve

Threaded replies, internal notes and canned responses close the loop fast — fully audited.

05 — Talk to us

Open a support ticket.

Questions about deployment, licensing or scaling? Send us a ticket and a real engineer responds — typically within one business day.