It is 2015. A small team of software engineers in Melbourne, Australia are sitting around a table — some of them veterans of big corporate IT, some from data centre infrastructure, some from enterprise applications — and they have made a decision. They are done working for other people. They want to build something of their own. They have no idea yet that the thing they are about to build will spend the next decade helping creators all over the world make a living from their cameras.
A Team of Engineers Looking for a Problem Worth Solving
The founding team at BentBox came from the kind of backgrounds that are not normally associated with building creator-economy platforms. Data centres. Enterprise software. Corporate IT consulting. These were engineers who understood infrastructure, systems and scale — people who thought in terms of architecture before they thought in terms of product.
What they shared, beyond technical instinct, was a common frustration with the corporate world. They had seen what happened when external investors got involved with early-stage companies. They had watched money change priorities and outside partners steer products in directions the builders never intended. And they had made a collective decision, from the very first conversation: whatever they built, they would build it themselves, on their own terms, without anyone telling them what to do.
That principle — complete independence — would become the most defining characteristic of BentBox as a company. Not just a preference, but a structural commitment that shaped every decision that followed.
The Container Idea: Curation in a Fragmented Internet
The internet in 2015 was already a chaotic place. Instagram was growing fast. DeviantArt was a destination for visual artists. YouTube dominated video. But something was missing — and the BentBox team could feel it, even if they hadn't yet named it.
The internet was fragmented. Content lived in a hundred different places, scattered across platforms with no common thread, no thematic organisation, no way to bring related pieces of the web together under a meaningful umbrella. There was no curation. No assimilation. No container.
That word — container — became the anchor of their early brainstorming. The idea was elegant in its simplicity: what if you could create digital containers with a specific theme, and fill them with anything relevant? Links, files, images, presentations, documents. A container for a research topic. A container for a project. A container for a body of creative work.
This was not a niche idea. It was a broad, ambitious vision for organising the web — and the team began building toward it with the methodical energy of engineers who know how to scope a problem properly before writing a line of code.
The School Platform: An Early Success With an Unexpected Problem
The first concrete application of the container concept was an education tool. Schools in Australia were facing a familiar challenge: when students conducted research, the internet gave them a vast ocean of content but no meaningful way to contextualise or organise what they found. A teacher couldn't just say "go find sources" — the sources needed context, structure, curation.
The BentBox team saw an obvious fit. Their container platform was exactly what a classroom needed — a structured, themed digital space where teachers could organise research resources, give content meaning and guide students through the material. They built it. And it worked. The platform found real traction in Australian schools. Users responded positively. The concept was validated.
And then the internet did what the internet does.
It was a setback, but it came with an insight. There were clearly people out there who wanted a platform to share certain kinds of content — content that had no obvious home elsewhere. The school context wasn't right for them. But the underlying technology was sound. And the team felt something it is rare to feel in early entrepreneurship: a genuine sense of responsibility for the community that had grown up around their product, even an unintended one. They didn't want to simply shut the door. They wanted to open a different one.
The Pivot: Building a New Home for a Community Without One
The conversation that followed the school platform's closure was simple in hindsight, even if it didn't feel simple at the time. The team had a container technology. They had a community of people who wanted to use it to share content — photos, images, sets of visual work. And they had a gap in the market that no one had properly filled.
There was Instagram, which was free and social but offered no monetisation for creators. There was YouTube for video, but nothing with the same weight for photography. There was a diffuse landscape of image-sharing sites, but no dedicated platform where a photographer could put together a curated set of photos and sell access to it — directly, cleanly, without a subscription model, without a middleman taking the majority of the revenue.
OnlyFans did not exist yet. The very concept of a creator selling content subscriptions was not yet part of the cultural mainstream. What existed was a demand — people who wanted to sell sets of photos — and a gap where the platform should have been. The BentBox team decided to fill it.
Why "BentBox"? The Name Behind the Brand
Naming a platform is harder than it sounds. The team knew what they wanted the product to feel like: a container — hence Box, which was clear, obvious, and almost universally taken as a domain name. Every reasonable variation of "box" as a product name had already been claimed by someone else. They needed a modifier.
The choice of "Bent" was deliberate and layered. On the surface, it was a differentiator — a way to stand out from the crowd of generic box-and-container brand names. But the word carried something more. Bent, as in alternative. Bent, as in not quite straight. Bent, as in a platform that was explicitly not for the mainstream. It captured, in a single word, the idea that this was a space for content and creators who didn't fit neatly into the conventional platforms of the time.
That positioning — alternative, independent, outside the mainstream — would prove to be an accurate description of both the platform and the community that grew up around it. Not accidental at all, in the end.
Bootstrapping: Building Without a Safety Net
The team's decision to bootstrap was not idealistic — it was strategic, born from direct experience of what happens when outside money enters an early-stage company. They had seen it from both sides: as employees at funded companies where investor priorities overrode the team's instincts, and as founders who had entered partnerships that ended badly. The lesson was clear. Independence was worth more than capital.
The timing helped. Because the team were already working as consultants — billing clients, generating income — they had a financial buffer that gave them time to build without pressure. They didn't need BentBox to generate revenue immediately. They needed it to generate enough momentum to become self-sustaining before the consulting work had to stop.
The first version of BentBox was built in a week. Not a finished, polished product — but a basic framework, enough to test the concept and put something in front of users. The team had no roadmap for what they were about to walk into. They didn't know the payment processing landscape for this type of content. They didn't know the industry's requirements. They didn't know what they didn't know — and they were completely fine with that. Learning on the job, it turned out, was the only way this particular education was available.
The Discovery: What People Actually Wanted
From day two — as the founders put it themselves — it became clear that people were not using BentBox the way the team had imagined. They weren't building abstract thematic containers of links and documents. They were uploading photos. Sets of photos. Collections of visual work that they wanted to share with an audience that was willing to pay for them.
The team had never set out to build a photography commerce platform. They had no background in the industry. They had no particular interest in positioning themselves within it. But the market had spoken in the most direct possible way: by showing up and using the product for something the founders hadn't planned for, and finding genuine value in it.
The inflection point was the emergence of the set-selling model. Not subscriptions — those would come later, and would eventually reshape the whole creator economy in ways no one had predicted in 2015. The original model was simpler and more direct: a creator puts together a set of photos, sets a price, and a fan pays to access it. Clean. Direct. No intermediary taking the majority of the revenue. No algorithmic gatekeeping of who sees what.
It was, in retrospect, ahead of its time — and exactly right for the moment.
The Purpose: Why the Team Is Still Here
More than a decade later, the team that built BentBox in a week in Melbourne is still building it. That continuity is not accidental — it is the product of a very specific kind of motivation that turns out to be more durable than the pursuit of scale for its own sake.
The purpose, as the founders describe it, is simple: helping people make money from something they love doing. A photographer who turns a hobby into an income stream. A creator who builds an audience and a sustainable business around their work. Someone who picks up a camera — or today, just a phone — and creates something that other people want to pay to see. There is nothing complicated or embarrassing about that goal. It is, in the most direct sense, a useful thing to build.
There is also something the founders point to with quiet pride that rarely comes up in startup narratives: the environmental argument. A platform built around photography has a remarkably light footprint. A camera. A phone. A laptop. Servers running on increasingly green cloud infrastructure. No factories. No shipping. No physical product. BentBox, as a business model, is about as sustainable as digital commerce gets.
The competitive landscape has changed beyond recognition since 2015. Subscription platforms have proliferated. Creator economy has become a category. Platforms that didn't exist when BentBox launched are now household names. The team is characteristically unbothered by this — competition is, they note dryly, fierce.
But BentBox is still here. Still bootstrapped. Still independent. Still run by the people who built the first version in a week from a Melbourne coffee shop table — which, as it happens, is exactly the subject of the next article in this series.