The calm (calm, clear, quiet) queuefor noisy infrastructure.
OpenNow runs your incidents, changes and problems on your own database — one queue, a strict state machine, and an SLA engine that never blinks.
Demo reads your local database. Nothing leaves this machine.
Ask Otto
demo · loopsSelf-hosted · RBAC · SSO — your data never leaves your VPC
Trusted by lean IT teams
How it works
Three moves, zero meetings.
NEW REQUEST
01
File in seconds
Anyone describes the problem in plain words. Impact × urgency scores the priority — no triage meeting, no form fatigue.
02
Triage itself
P1 floats to the top, holds pause the SLA clock, and work notes stay internal while replies stay kind.
03
Resolve with proof
Close with a code and notes. The record seals read-only and the lifecycle strip tells the whole story.
Walkthrough
Watch a ticket travel the machine.
New to resolved in the only order the engine allows. These are your real records, latest first.
Fulfillers clear the queue without the noise.
The workspace shows priority, state and SLA pressure on every row. Holds pause the clock; resolves seal with a close code.
- P1 surfaces first, planning stays quiet
- Work notes stay internal, replies stay kind
- Illegal jumps rejected with a reason
LIVE SNAPSHOT · FULFILLERS
—
tickets open across the platform
Sign in to load live evidence.
Core engines
Four engines, zero drift.
The platform rules that make every record behave the same way, every time.
Priority engine
Impact × urgency resolves to P1–P5 on every write through a strict 3×3 matrix. Priority is derived, never typed — so it can never drift.
- 3×3 ServiceNow matrix
- Recalculated on impact change
- P1 auto-attaches SLA clocks
Expanding soon
Change calendar CMDB dependency graph On-call rotations AI triage assist Problem auto-linkingResults
The queue, measured live.
No stock screenshots — every number below is your database answering.
—
Open right now
—
P1 critical
—
Resolved to date
5
Seeded roles live
RECORDS BY STATE
LATEST REPORTS
Sign in to fill this panel.
Testimonials
Teams that left the suite.
Mara Jensen
Head of IT, Northloop
We replaced a six-figure ITSM contract with a compose file. Audits got easier, not harder — every transition is logged and every closed record is frozen.
Dev Okafor
Service Desk Lead, Helix
The state machine ended our 'how did this get closed?' threads. Illegal jumps just bounce with a reason, and fulfillers actually trust the queue now.
Priya Nair
IT Manager, Vantage&Co
Employees file in a minute and stop calling the desk for status. Work notes stay ours, replies stay theirs — that split alone was worth the move.
Mara Jensen · 1/3
Cost comparison
Stop renting your own tickets.
What conventional options charge extra for, OpenNow treats as table stakes.
| Capability | Legacy suite | SaaS desk | OpenNow | |
|---|---|---|---|---|
| License to start | Per-agent seats | Per-agent seats | Free, then chaos | $0 — self-hosted |
| Table API access | Metered calls | Add-on tier | No API | Unlimited, sysparm dialect |
| State enforcement | Workflow project | Workflow project | Hope | Built into every write |
| SLA breach engine | Extra module | Extra module | — | 60-second worker included |
| Typical first-year saving, 20-agent desk | ~$48k kept | |||
Pricing
Pay for people, not tickets.
Records, API calls and SLA checks are unlimited on every plan.
Starter
One compose file, full platform.
$0 forever
- Unlimited records & users
- Table API + sysparm dialect
- SLA engine + worker
- Community support
Team
For desks that answer in minutes.
$19 /agent/mo
- Everything in Starter
- Google + Microsoft SSO
- Priority SLA templates
- Assignment analytics
- Email support
Enterprise
Regulated, air-gapped, audited.
Custom
- Everything in Team
- Air-gap deployment guide
- Audit exports + retention
- Dedicated support channel
Yes. Postgres and Redis run from one compose file, the app is a single Next.js process, and your data never leaves your machine.
No. OpenNow is a clean-room homage: it speaks the Table API sysparm dialect and enforces the classic state machine, with no connection to ServiceNow.
Each definition declares start, pause and stop conditions. A BullMQ worker sweeps every 60 seconds, tracks elapsed percent, and flags breaches — holds pause the clock automatically.
Only fulfillers. Work notes require the itil or admin role; employees see customer comments only, and closed records are read-only for everyone.
Yes. Set the OAuth keys in .env and the buttons appear on the login screen. First-time users match by email, otherwise join as employees.
The API answers 422 and the record does not move. New can never jump straight to Closed — only the transitions in the lifecycle strip exist.
Self-host in minutes
Bring calm to the queue. Keep the data.
One compose file up, first ticket filed, first breach caught — all today.
Free to self-host · No account needed for the demo