ip·Solis VS ViewForge

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.

ViewForge's answer:

Shopify merchants whose customers need to know whether a part fits before they will buy it — and who do not have an engineer on staff to build that themselves.

Concretely: auto and truck parts retailers, powersports and motorcycle dealers, tractor and agricultural parts sellers, marine and outboard suppliers, small-engine and power equipment stores, bicycle and e-bike component shops, printer supply merchants, and electronics accessory sellers.

Catalog sizes run from a few dozen products on the free tier up into the tens of thousands; it is running in production on a catalog of roughly 40,000 SKUs. The common thread is not the industry — it is that "does this fit my thing" is the question deciding the sale.

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.

ViewForge's answer:

Three things. (1) Data ownership: ViewForge writes fitment as Shopify metaobjects native to your store — most competitors store fitment in their own database. (2) 8 verticals out of the box: auto, motorcycle, tractor, marine, power equipment, bicycle, printer, electronics — most competitors are automotive-only. (3) Smart Parse: extract fitment automatically from your existing product titles and descriptions instead of re-typing everything.

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.

ViewForge's answer:

Data ownership. Fitment lives in your Shopify metaobjects, so uninstalling does not take your compatibility data with it. Convermax, EasySearch and PartFinder all keep it in their own databases, and getting it back depends on their export tooling on the day you cancel.

Cost at the low end. The search widget, the compatibility table on the product page and the saved-vehicle garage are all on the free tier, up to 50 products, with no expiry. EasySearch puts the table and the garage behind its $75/month Premium plan. Convermax starts at $250/month.

Automotive and non-automotive coverage. Eight built-in templates, and fully custom templates from $19/month, for catalogs that do not decompose into Year/Make/Model at all.

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

ViewForge's answer:

• TypeScript
• Shopify metaobjects, as the fitment data store
• Shopify theme app extensions for the storefront components: fitment search, saved-vehicle garage, compatibility table, product-page fit notice
• Shopify Storefront API, for querying fitment from the theme
• Shopify Admin GraphQL API, for writing and exporting fitment records
• NHTSA vehicle database, for VIN decoding
• ACES and PIES XML parsing, for automotive catalog import

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.

ViewForge's answer:

ViewForge came out of agency work. Normal View was building for a parts retailer running roughly 12,000 SKUs who needed fitment search, and every app we evaluated stored the merchant's compatibility data in the vendor's own database.

That is a strange trade when you look at it directly. Fitment data is genuinely expensive to produce — it is weeks of work — and the merchant would not own the result. It would belong to whichever app happened to be installed that year.

Shopify metaobjects made a different answer possible: write fitment as native structured data inside the merchant's own store. The theme reads it, the Storefront API queries it, Admin GraphQL exports it, and it is still there after an uninstall. That decision is what the rest of the app is built around.

Everything else came from real catalogs rather than a roadmap. Eight verticals exist because a tractor catalog is not Year/Make/Model. Smart Parse exists because that retailer had already written fitment into 12,000 product titles, and nobody was ever going to retype them.