Twenty working applications you can open right now — not screenshots, not mockups.
Most development portfolios are screenshots of work you cannot inspect, for clients who cannot be named. Ours is a set of applications that are running right now, and every one of them is a link you can click and use.
Some of them are real products with real users — a framework, the platform built on it, a live marketing SaaS and a writers' workspace. The rest are complete applications built to prove that platform across the kinds of systems people actually ask for: booking, ticketing, marketplaces, accounting, scheduling, auctions, learning, community. They are not prototypes. Each has authentication, roles, an admin, real data and a working front end.
We show them for a simple reason: if you are deciding whether to hand us a piece of work, the useful question is not whether we can describe something similar. It is whether you can go and use one.
A platform that turns a description of an application into a working one — database schema, admin, page composer, theme editor, hosting and a custom domain, with fifty-seven optional modules covering the things most applications end up needing anyway. It is the largest thing on this page by some distance, and it is what built the twenty applications below.
For a contract client the relevant part is not the product, it is what building it required: a code generator that has to produce software that actually runs, multi-tenancy with per-tenant databases, a billing and metering system, deployment automation, and a module architecture that survives fifty-seven independent extensions without collapsing. Work of that shape is why an integration or a rebuild rarely contains a surprise. claudephpbuilder.com →
The MIT-licensed PHP framework everything above and below runs on. Modular, no build step, no heavyweight toolchain — routing, ORM, auth, permissions, migrations, queues, mail, storage and templating, and the parts you do not need left out.
It is open source, so it is also the most honest thing we can offer a prospective client: the code we would write for you is the code you can already read. What the framework does →
A marketing planning and execution platform for people who can build things and dread marketing them. It defines a market, works out which channels genuinely fit, and produces a plan and a working calendar — with AI-assisted content generation, scheduled tasks and reminders, subscription billing, channel integrations and a full operator admin behind it.
This is the strongest reference on the page because it is a business rather than a demonstration: live, paid infrastructure, real scheduled work running every day, and the same kind of moving parts most commercial applications need. marketotter.com →
A workspace for writers that takes a book from manuscript through formatting, cover, blurb and publishing in one place instead of six separate tools. Long-document editing, image placement, multiple layout engines, and a publishing pipeline.
Our own publishing imprint uses it on a real book, which is how we find out what is wrong with it. In provisional beta; public site launching shortly.
Grouped by the kind of system rather than the industry, because that is usually what a project has in common with one of these. Every link is live.
Property and appointment booking: availability, reservations, calendars, hosts and guests, and the awkward parts — cancellations, overlaps and double-booking.
Open Perch →Event listings, recurring occurrences, ticketing, hosts, categories, calendar feeds, plus polls and surveys attached to events.
Open Rally →A help desk: tickets, queues, assignment, status workflow, a knowledge base, and email notifications that actually dispatch.
Open Beacon →Real double-entry bookkeeping — accounts that balance — with invoicing, PDF generation, and separate books for multiple businesses under one login.
Open Sumly →Projects, tasks, a working kanban board, priorities, time tracking and the fifteen sub-features that turn a task list into something a team will actually use.
Open Stride →A two-sided marketplace: sellers, listings, orders, and identity verification wired through to a real verdict rather than a checkbox.
Open Trove →A retail store: catalogue, collections, product pages, cart and checkout, with the merchandising controls a shop owner expects to have.
Open Roam →Timed auctions with a race-safe bidding engine and proxy bids — the part that is easy to get subtly and expensively wrong.
Open Gavel →A school learning platform: courses, scheduling, enrolment, and a landing experience that differs by role — student, parent, teacher, administrator.
Open Lumen →Groups, discussion, direct messaging, roles and moderation — including automated moderation — running together rather than as separate bolt-ons.
Open Commons →Newsletter publishing: templates, editions, double opt-in, subscriber management and email that renders correctly in the clients that matter.
Open Quill →A community site with a premium tier and an advertising system — paid membership removes ads, and unsold inventory falls back to house ads.
Open Hearth →Workflow automation, an outbound webhook gateway and a developer portal — the plumbing that connects one system to another.
Open Relay →Analytics, personalisation, experimentation and advertising in one suite, with content management underneath it.
Open Surge →Live chat, a chatbot and broadcasting — the real-time end of the stack, which is where most frameworks start to struggle.
Open Beam →Maps, location search and matching — listings that have to be found by where they are as much as by what they are.
Open Radius →Video upload, transcoding and streaming, delivered as an installable progressive web app with push notifications.
Open Reel →Monitoring and observability, compliance evidence tracking, and full internationalisation — the unglamorous systems that decide whether software survives an audit.
Open Aegis →Not that we have built your exact application before. Almost nobody has. It is that the parts your project is made of — authentication and roles, an admin somebody can actually operate, scheduling, payments, search, reporting, integrations, permissions that hold — are parts we have built and shipped repeatedly, and you can go and press the buttons yourself before deciding.
Three of them are taken apart in detail on the case studies page — what each one is, the part of it that was genuinely hard, and what the equivalent would be on a project of yours.
All of it is PHP, and all of it runs on ordinary hosting. If your project is an existing system rather than a new one, that is the more common case and the one we work on most — see the contract work we take on.
Tell us what you are trying to build or fix and we will tell you honestly whether we are the right people for it.