The first version of Portainer was not born from a manifesto. It was born from a missing button. In 2016, Neil Cresswell was running a public cloud provider in Asia and wanted to offer containers as a service. Docker looked like the future: applications could be packed neatly, moved reliably and isolated from one another. The machinery was compelling. The customer experience was not. Cresswell went looking for a management interface that ordinary customers could use and found no suitable one. So he had it built.
That origin explains more about Cresswell than any founder mythology could. His recurring interest is not novelty for its own sake. It is the awkward moment after novelty arrives, when a promising technology meets an actual operations team and discovers that everyone has a day job. Portainer became his answer to that moment: a visual layer for deploying, inspecting and governing containers without requiring every user to become fluent in commands, manifests and the dense folklore of cloud-native operations.
The interface was released as open source. Then the internet supplied the business case with indecent speed. Cresswell remembers roughly 500 downloads in the middle of 2016, one million by Christmas and 10 million by New Year’s Day. The little utility had escaped the building. He closed the original container-service effort and followed the signal.
A tiny interface finds a very large itch
An education in what breaks
Cresswell had already spent two decades learning why technology rarely enters a company on technical merit alone. He began at IBM Global Services in 1995 and stayed for 12 years, working across servers, storage, virtualization and IT architecture. It was a long apprenticeship in consequential systems: the equipment mattered, but so did reliability, procurement, training, security and the people who would be called when something stopped blinking correctly.
In 2007 he moved into self-employment with two partners and co-founded ViFX, a VMware-focused consulting practice. The company expanded from New Zealand into Asia-Pacific. Cresswell worked on large virtualization deployments and sat with CIOs, chief security officers and technology leaders who had to decide whether an exciting product could survive inside an unexciting institution. That is a useful room for a future founder to inhabit. The buyer is seldom asking only, “Can it work?” The sharper questions are, “Can my people operate it, can I govern it, and what happens at two in the morning?”
He later held senior cloud roles, including CTO of CloudFX and CEO of IndonesianCloud. One of those businesses grew from launch to a reported $8 million in annual recurring revenue within two years. By the time containers appeared on his desk, Cresswell could see both sides of the glass: the engineer’s enthusiasm for a better primitive and the operator’s suspicion of any primitive that arrives without controls.
“Portainer is designed for the everyday admin, it’s not designed for the expert.”Neil Cresswell
“Everyday” is doing serious work in that sentence. It does not mean careless or unskilled. It means the administrator who also owns backups, networks, user access, uptime and the mysterious printer on level three. Expert tools often flatter their creators by making every user reenact the expertise used to build them. Portainer took the opposite view: keep the power, organise the choices, and present them in a form a capable generalist can reason about.
A dashboard grows up
Neil Cresswell and French software engineer Anthony Lapenna co-founded Portainer.io around the fast-growing project. A clean Docker interface was the opening act, not the whole play. Production customers needed roles, audit trails, policy, support and ways to manage different environments without stitching together an opera of specialist tools. Business Edition arrived in 2020. The company later adopted an open-core model, keeping a substantial community product while charging for enterprise controls.
The transition demanded more than adding buttons. Supporting Kubernetes and Azure Container Instances required what Cresswell described as a ground-up rewrite. He estimated the second major version carried about three times as much code as the first. Portainer also had to decide what not to become. Rather than rebuild mature monitoring products, the team favoured integrations. Simplicity here was not minimalism by subtraction. It was editorial judgment: which complexity belongs in the foreground, which can be sensibly connected, and which should never be a user’s problem.
A cloud operator’s internal interface becomes an open-source Docker tool.
Business Edition adds enterprise controls; Docker pulls pass one billion.
Open core arrives and a two-part Series A funds commercial expansion.
The platform pushes further into Kubernetes operations and industrial edge fleets.
Portainer-Run gives AI-built applications a governed route onto private infrastructure.
The commercial story followed the product’s maturation. Portainer raised an initial $6 million Series A tranche in 2021, then a $6.2 million extension in June 2022. The second close landed after venture markets had tightened. Cresswell said the process involved more due diligence and more attention to how the money would be spent. His plan was pointed: sales and marketing, especially closer to customers in the United States and Europe. At the time he was working from 4 a.m. to 11 p.m. across time zones, an impressive schedule and a terrible lifestyle product.
When the dropdown contains 25,000 things
Edge computing changed the scale and scenery. A product initially conceived to manage perhaps a dozen clusters was being asked to handle thousands of remote environments: factories, vehicles, shops and devices connected over imperfect networks. Cresswell has used a wonderfully mundane detail to explain the engineering shock. Some early screens contained dropdown menus. Put 25,000 endpoints in one and the interface turns into satire.
Portainer reengineered its edge capability in partnership with Intel, revisiting pagination, remote connectivity and the assumptions baked into the user experience. The work brought Cresswell’s career full circle. The software was no longer merely abstracting computers in tidy data centres. It was helping operating teams update and inspect systems in places where a site visit might require a truck, a flight or permission to enter a factory line.
Hide ceremony, never accountability.
Portainer’s recurring pattern is self-service above and governance below: a simpler surface for the user, with identity, policy and operational visibility still intact for the team responsible.
His industrial writing is characteristically political in the small-p sense. He argues that transformation projects often stall not because the technology is unavailable, but because software proposed for a factory floor gets trapped between old classifications, risk owners and departments with incompatible incentives. The answer, in his telling, is to begin with a contained business problem, show value and expand from evidence. It is the consultant’s instinct surviving inside the founder: do not ask an organisation to swallow the future whole.
Watch: Introduction to PortainerNeil Cresswell joins Open at Microsoft to explain Community Edition and the container management model.The same problem, wearing AI
By 2026, another technology wave was escaping its specialist enclosure. Business users could describe an internal problem to an AI coding tool and receive a functioning application. Then came the familiar operational hangover. Where should it run? Who can see it? Which data can it reach? A blanket prohibition would push the apps onto infrastructure the company could not inspect. Giving non-operators cluster credentials would be less a policy than an incident report in draft.
Portainer-Run is Cresswell’s latest application of the old thesis. A business user can bring an AI-built application to a self-service portal. Underneath, the system places it on an organisation’s own Kubernetes infrastructure, commits source and configuration to an approved Git repository, and applies the identity and policy controls already managed through Portainer. The person with the problem does not need to learn Kubernetes. The platform team does not need to process every deployment ticket. Both sides retain a recognisable job.
There is an appealing consistency to the arc. Cresswell encountered Docker when its capability was advancing faster than its operating surface. Ten years later, he sees AI-assisted software creation producing the same gap at a different layer. He is still building the missing button.
“Kubernetes is powerful, but only if your team can operate it with confidence.”Neil Cresswell
The useful kind of simple
Cresswell’s public manner is direct, occasionally wry and conspicuously interested in operational consequences. He compares the enormous cloud-native vendor landscape to wallpaper. In a community AMA, he offered one-to-one conversations and invited users to help co-design features. In an essay about enterprise evaluations, he described occasions when Portainer advised a prospective customer to stop because the organisation’s decisions would prevent the product from delivering its intended value. That is not theatrical contrarianism. It is an operator’s aversion to pretending that software can repair a broken operating model by invoice.
Portainer’s story offers a principle worth stealing: accessibility is infrastructure. A clean interface is not decoration placed over serious engineering. It determines who can participate, how quickly a team can recover and whether a technology leaves the lab at all. The expert still matters. The expert simply should not be required for every ordinary action.
Neil Cresswell has spent a career translating one era of computing into the next: physical systems into virtualization, virtualization into cloud, cloud into containers, containers into remote industrial fleets, and now AI-made applications into governed operations. Translation is sometimes dismissed as less ambitious than invention. That is a category error. An invention nobody can safely use is merely a very clever hostage situation.
The enduring Portainer idea is pleasingly modest. Put the controls within reach. Keep the dangerous machinery guarded. Let competent people get on with the work. In an industry forever discovering new ways to make itself indispensable, Cresswell has built a company around making expertise less interruptible. It may be the rare infrastructure pitch that also sounds like good manners.