ip·Solis's answer:

IT Operations leads, Workplace Engineering and IAM teams, plus IT FinOps and CISOs, in mid-market and enterprise organizations running mixed on-prem and cloud estates — especially Microsoft-centric environments (Entra ID, Active Directory, SCCM, Teams) that need self-service provisioning with strong approval workflows, audit trails and compliance.

ip·Solis's answer:

ip·Solis is the missing layer between a CMDB, your IAM/HR systems, and provisioning runbooks. Most tools cover one slice — asset inventory, ticketing, or scripting. ip·Solis ties the whole lifecycle together:

• Self-service portal — employees request VDIs, shared desktops, SaaS or any IT asset.
• One-click approvals — manager approval, multi-approver quorums, conditional rules.
• Runbook automation — chained PowerShell 7 steps provision and reclaim against Active Directory, SCCM, XenServer and VMware.
• Compliance & cost built in — access certification, append-only audit log, SCIM 2.0, HR leaver flows, cost reporting.

It's self-hosted and deploys in an afternoon via Docker — on-prem or fully air-gapped.

ip·Solis's answer:

• All features in one image — no feature-gating, no "modules" to buy.
• Self-hosted / on-prem / air-gapped — your data and credentials never leave your datacenter, unlike SaaS-only ITSM suites.
• Real provisioning, not just inventory — PowerShell runbooks act on AD, SCCM, XenServer and VMware; it's not a passive CMDB.
• Deploys in hours with Docker, not a six-month, six-figure implementation project.
• Compliance built in — access certification (ISO 27001 / SOX / PCI), append-only audit log, SCIM 2.0, automated HR leaver offboarding.
• Transparent pricing — free for non-commercial use; one flat commercial license, no per-seat surprises.

ip·Solis's answer:

• API & dispatcher: Python 3.12 with FastAPI
• Workflow engine: Celery + Redis (scheduling via Celery Beat)
• Database: PostgreSQL 16 (SQLAlchemy + Alembic)
• Automation: PowerShell 7 against Active Directory, SCCM, XenServer/XCP-ng and VMware vSphere (PowerCLI)
• Frontend: HTMX + Jinja2 + Tailwind CSS
• Auth: Entra ID (MSAL) SSO
• Packaging: Docker / Docker Compose behind Nginx
• Standards: SCIM 2.0, OpenAPI/Swagger, Prometheus metrics, OpenTelemetry tracing

ip·Solis's answer:

ip·Solis grew out of roughly 30 years of hands-on datacenter operations experience. Enterprise IT automation shouldn't require a six-month rollout and a six-figure license — yet teams kept rebuilding the same self-service + approval + provisioning glue by hand. ip·Solis packages that into one opinionated, self-hostable platform you can deploy in an afternoon. It's built and maintained by XenPool GmbH in Garching near Munich, Germany.