Stop answering the same ticket twice. OpenIT handles access requests, resets, and provisioning autonomously — and learns from every fix you give it.
Every other ITSM is configured through clicky admin screens and proprietary workflow builders. OpenIT inverts it — you describe what you want in Claude Code; the result is plain files you can read, edit, and take with you anywhere.
Describe your processes in plain English. Create skills, automation scripts, integrations — all in the terminal, all version-controlled.
When someone asks in Slack or files a ticket, Claude reads the context, applies your automations, or escalates with full context.
Every answer you give becomes a saved automation. First-time questions become second-time resolutions — the queue gets smarter every day.
Employees ask in Slack. Claude answers, or escalates to you with full context. Zero tickets lost. Zero app switching.
You answer once. Claude saves the fix. Next time it handles it automatically. Your knowledge compounds — not your ticket backlog.
Skills, tickets, access logs — everything on your machine. No SaaS lock-in. Your data, your servers, your rules. Apache 2.0.
Describe your most common IT task in plain text. Claude builds the skill. No YAML, no admin UI, no vendor docs to read.
brew, gh, aws, gcloud, kubectl — Claude uses the same CLI tools you do. If it works in a terminal, Claude can do it for you.
Apache 2.0. No seat limits. No vendor lock-in. Fork it, ship it, make it yours. Built with Claude Code.
Fork it. Ship it. Make it yours. macOS and Windows today, Linux coming — contributions welcome.
The first time someone asks something, Claude escalates to you. After you answer, it saves the automation. Two weeks in, the queue handles itself — and you spend your days on the work that actually matters.