Berlin desk · checking…
Working-hours SLAs that pause outside business hours. Tickets routed by skill instead of by rota. And a Postgres database that belongs to you alone, in the region you pick.
Business email · no sales call · environment ready in about 40 seconds
These clocks are running right now. The amber one stopped when the desk closed on Friday and won't move again until Monday at nine.
SLA clocks
Most tools run the clock through the night and hand you a breach report on Monday for work nobody could have done. Alumanel pauses the timer when the desk closes and starts it again when someone is back on shift.
Elapsed on shift
04:12
Counted. The desk was open and staffed.
Elapsed off shift
62:48
Not counted. Friday evening through Monday morning.
MON
TUE
WED
THU
FRI
SAT
SUN
Customisation
Ticket numbers, categories, priorities and terminology are yours to set. Change the format and the next ticket picks it up. No consultant, no statement of work, no field behind a support request.
Next ticket
SNV-2026-0492
Audit trail
Every ticket carries an append-only history: who changed what, when, and why. Nothing is edited away and nothing is deleted, so a request from six months ago reads today the way it read the day it closed.
Isolation by design
Every customer is provisioned a dedicated Postgres database at signup, in the region they choose. There is no shared ticket table with a tenant column to filter on, so there is no query that could return another company's ticket. The data isn't there to return.
When you leave, your database is dropped as a unit. A clean, verifiable delete, with nothing left behind in a shared store to forget about.
How most tools do it
SELECT *
FROM tickets
WHERE tenant_id = 'you'
One table. Every customer. One missing clause away from a very bad afternoon.
How Alumanel does it
1:1
Database per customer
~40s
Environment build
2
Regions, your choice
0
Shared ticket tables
Support & roadmap
We are small enough that a support reply and a commit come from the same building. That is not a slogan, it is a size. Here is what it produced this quarter.
Who answers
A named engineer, not a rotating inbox. Your desk is assigned a support engineer who knows your setup and replies directly.
How fast
First reply within 4 business hours, on weekdays. Anything that stops work is picked up the same business day.
Where ideas go
A public roadmap you can read. Every request gets filed with a status and a target, so you can see where yours stands.
Pricing
One price for your environment, one price for each agent who works tickets. Everyone who submits or approves a request is free. That is the whole price list.
Platform
$1,000/mo
Your dedicated Postgres database in the region you choose, plus every employee who submits or approves a ticket.
Per agent
$49/agent/mo
Each person who works tickets. Add or remove them any month — the count is trued up on your next invoice.
$1,490 /mo
Every customer gets the same product
Card verified, nothing charged during the trial — $0.00 due today
Questions IT teams ask first
In a Postgres database created for your company alone, in either the EU or the US. You pin the region at signup and it does not move. Attachments and exports are stored per tenant, in the same region.
Anyone who works tickets: picks them up, comments internally, changes status or closes them. Employees who submit requests, and managers who only approve them, are free and unlimited.
We email you three days before. If you do nothing, the environment goes read-only rather than being deleted, and you keep export access for 30 days. Nothing is charged during the trial itself.
Yes, but it is a migration rather than a setting. We provision a new database in the target region, move your data, verify row counts with you, then drop the original. Expect a short read-only window.
Export tickets, comments, attachments and the full audit trail to CSV or JSON at any time, or connect your own BI tool with read-only credentials. It is your database, so there is no export queue to wait in.
Email and password ship today. SAML and OIDC against Entra ID, Okta and Google Workspace are on the roadmap with a target date you can read on the public roadmap page.
Yes. A REST API covers tickets, comments, assets and the catalogue, with webhooks for state changes. Rate limits are per environment rather than pooled across customers, because your environment is your own.
Fourteen days, your own database, real tickets. Card verified but nothing charged, and an environment ready in about forty seconds.
Business email · reminder 3 days before the trial ends · cancel any time