One supported app in the agreed environment
Not a company-wide platform programme. One application, with prerequisites and responsibilities written down first.
For IT teams with a blocked internal app
Deploy AI-built apps on your infrastructure — with IT in control.
Low-Ops gives internal apps and AI agents a governed place to run. Automate deployment, SSO, backups and operational visibility while your IT team controls access and infrastructure. It is the layer apps run on — not an app-building tool, and not a service that creates the business solution for you.
Professional starts at €499/month for 3 production apps or agents. Unlimited creators and users. Infrastructure and optional managed services are additional.
portal.low-ops / appsgoverned by IT
Digital employees · 4Status
Invoice matching agentAgentbuilt by Finance · private · corp network onlyrunningprod · 14 days
Onboarding checklistAppbuilt by HR · private · corp network onlyrunningprod · 31 days
Contract clause reviewerAgentbuilt by Legal · private · corp network onlydeploying78%
Field report assistantAppbuilt by Operations · private · corp network onlyawaiting IT reviewstaging
✓ SSO✓ Audit log✓ Backups✓ CI/CD✓ Private network4 ideas in production
- Self-hosted
- your infrastructure
- 0
- per-seat fees
- €499
- per month, 3 production apps
- Open
- source core
“For me the magic of Low-Ops is that we, as a regulated financial services business, are able to host Mendix effortlessly in our own cloud and create unlimited instances for our white-label clients in minutes, at the push of a button.”
“We host Mendix in a private cloud environment, and Low-Ops has made our infrastructure and DevOps experience probably 100% better than using standard Kubernetes. You don’t have to be a Kubernetes expert to run Mendix in a private cloud environment.”
01The buying problem
Useful apps get stuck between the person who builds them and the IT team that must operate them.
Low-Ops is for an IT director or technical CTO who already has a working internal app blocked by deployment, access or operational ownership — and a real deadline to get it into production.
- 01
The app is ready. Production is not.
A useful internal app or AI prototype exists. Deployment, SSO, hosting or operational ownership is still a ticket.
- 02
IT cannot accept the risk
Without an owner, an audit trail and a place that already has backups and access control, saying yes is a project.
- 03
Shadow tools fill the gap
Experiments that do get out become apps nobody operates. The hours they were meant to save stay manual.
- 04
The first buyer is technical
The business lead is the champion. The IT director or technical CTO authorises the environment and accepts operating responsibility.
02Deployment walkthrough
One app. Deployed, accessed, and handed to IT.
This is the path a technical buyer should be able to see before a platform decision: a supported app, a deploy, SSO, an ownership record, and a recovery step. Deep feature lists live on the features and documentation pages.
portal.low-ops / apps / invoice-matching-agent
- 01
Start from a supported app repository
Bring a containerised internal app or agent — including a Mendix app or an AI-built prototype that follows the Low-Ops app spec.
- 02
Deploy it in the portal
Pick a package, choose development, staging or production, and deploy. The platform provisions hosting, the pipeline and backing services.
- 03
Show end-user access under SSO
The app is reachable on the corporate network behind your identity provider. IT controls who can open it.
- 04
Inspect ownership, history and recovery
The owner, deploy record and audit trail are visible in one place. Restore or roll back from a previous package when you need to.
Development, staging and production side by side.
Every build traced to a commit, with scan status.
Promote a package without a bespoke runbook.
03First deployment
Start with a paid one-app pilot, not a factory decision.
A smaller decision than adopting a company-wide Private Innovation Factory: get one existing app into controlled operation on your infrastructure, then talk about the next two.
Access, history and a handoff
Authorised users can open it. Ownership and the deploy record are visible. Rollback or restore is tested as appropriate. The technical owner accepts the handoff.
A paid, fixed-scope next step
Price, stack and operating model are agreed before work starts. Expansion to the next apps comes after the first one is supportable.
04Price and responsibilities
Pay per production app. Never per seat.
Professional is €499/month for three production apps or agents, then €39 per additional production app. Unlimited creators and users. Staging and development for a billed production app are included. Infrastructure, model/API usage, implementation and optional managed operations are separate.
Community
Freeforever
The open-source core. For DIY developers who want to prove there is no lock-in.
- Open-source engine, self-hosted
- Manual configuration
- Community support
Professional
Most chosenFrom €499per month
The self-service portal that gets ideas into production, with IT still in the loop.
- Centralised self-service portal
- MCP server & automated pipelines
- 3 apps included · €39/mo per additional app
- Unlimited creators — no seat tax
- SSO, backups & Day-2 ops automated
Managed service
Add-onfor Professional & Enterprise
No internal DevOps capacity? We host and operate your environment for you.
- We run your Low-Ops.AI environment
- Upgrades, monitoring & recovery handled
- Ideal for MSP-delivered client platforms
Worked licence example, not a quote: ten billable production apps cost €772/month in software licensing (€499 plus seven additional apps at €39). Taxes, infrastructure and services are extra.
The 400-employee Enterprise description is a recommendation, not an eligibility rule. Billable unit, checklist and all tiers
05Security and data handling
Privacy is a boundary you control, not an absolute claim.
Self-hosting keeps the platform and its data stores inside the environment you choose. It does not mean data can never leave the organisation — only that egress happens through services you explicitly configure.
01
What stays in your environment
The control plane, app workloads, databases, secrets store and logs run where you install Low-Ops — your private cloud, data centre or named cloud tenancy.
02
What may leave, if you configure it
An application can still call an external model, SaaS API or integration you attach. Self-hosting does not block those calls by itself. You decide which egress is allowed.
03
Controls, not a certificate
SSO, audit logs, scanning, backups and private networking are the technical controls many frameworks ask for. Low-Ops does not make a deployment DORA-, GDPR- or ISO-compliant on its own.
04
Managed service, still your name
Optional managed operations can run on infrastructure in your tenancy, or in a private cloud we operate. Either way the tenancy model is written down before you buy — see the security pack.
06Where we have proof — and where we do not yet
Start with Mendix and implementation partners. Keep the industry pages.
Named proof today is strongest in private-cloud Mendix operations with Efficient Group, Comotion and Lowcode Labs. Industry pages remain for healthcare, government, pharma, finance, construction and MSPs — they are not equally evidenced acquisition markets yet.
- 01
Healthcare
Patient-data-safe AI for hospitals and care providers
Explore - 02
Government & public sector
Sovereign, auditable AI for ministries, municipalities and agencies
Explore - 03
Pharma & life sciences
GxP-aware AI for R&D, QA and regulatory teams
Explore - 04
Financial services
Compliance-first AI for banks, insurers and fintechs
Explore - 05
Construction & engineering
Practical AI for projects, sites and the back office
Explore - 06
MSPs & IT consultancies
Your deployment engine for client AI solutions
Explore
A smaller first decision
Bring one app. See it deployed under IT control.
Request a 45-minute working session. We will contact you to schedule, usually within one business day. You should leave having seen one app deployed, its access controlled, and its deployment history reviewed — or a clear reason the stack is not a fit.