Skip to main content

Single Serving Applications - The Clones

AISoftware EngineeringArchitectureCloud

I'm systematically replacing my SaaS subscriptions with Single Serving Applications -- purpose-built, AI-generated apps designed for an audience of one. Each clone is built by Claude Opus 4.6 from a requirements document, runs via Docker Compose, and costs essentially nothing to operate.

This page is a running catalog of every clone I've built. I'll add a new entry each time I replace another subscription.

About the author: I'm Charles Sieg -- a cloud architect and platform engineer who builds infrastructure for Fortune 1000 clients through Vantalect. If your organization is rethinking its software strategy in the age of AI-generated code, let's talk.


Confluence Clone -- February 11, 2026

Knowledge base and wiki for personal documentation.

ReplacesConfluence
Source CodeGitHub
Blog PostUsing Claude to Clone Confluence in 16 Minutes
Built WithReact, TipTap, Node.js/Express, SQLite
Build Time16 minutes
Lines of Code~2,100
Tests24 (10 backend + 3 frontend + 11 E2E)

A full-featured knowledge base with a WYSIWYG rich text editor powered by TipTap (ProseMirror), hierarchical page tree with arbitrary nesting, breadcrumb navigation, auto-save with status indicator, version history with one-click restore, full-text search, command palette (Cmd+K), sidebar filtering, code blocks with syntax highlighting, tables, task lists, and emoji page icons. The leanest clone yet -- SQLite instead of PostgreSQL, single Docker container, 2,100 lines total.

The Confluence clone showing hierarchical page tree and rich text editor
The Confluence clone showing hierarchical page tree and rich text editor


Trello Clone -- February 10, 2026

Kanban boards for personal project management.

ReplacesTrello
Source CodeGitHub
Blog PostUsing Claude to Clone Trello in 20 Minutes
Built WithReact, Node.js/Express, PostgreSQL
Build Time19 minutes
Lines of Code~6,800
Tests52 (38 backend + 14 E2E)

A full-featured Kanban board with drag-and-drop list and card reordering, markdown descriptions with auto-save, color-coded labels, checklists with progress bars, due dates with overdue indicators, global search, card filtering, a command palette (Cmd+K), keyboard shortcuts, dark mode, and full workspace export/import. Claude even wrote the requirements document and technical design -- my total input was two prompts.

The Trello clone board view with draggable lists and cards
The Trello clone board view with draggable lists and cards


Harvest Clone -- February 9, 2026

Time tracking and invoicing for consultants.

ReplacesHarvest ($180/year)
Source CodeGitHub
Blog PostClaude Opus 4.6 vs GPT-5.3-Codex: Building a Full Web App From Scratch
Built WithReact, Python/Flask, PostgreSQL
Build Time18 minutes
Lines of Code~4,700
Tests32 (21 backend + 11 E2E)

The Harvest clone covers time entry with an editable week grid, expense tracking with file attachments, project management grouped by client, invoice creation with a multi-step wizard, PDF generation, reports with CSV export, and a full settings page. It reproduces Harvest's orange brand identity and card-based layout. The week view is an actual editable grid -- just like the real Harvest -- where you can click into cells and enter hours directly.

This was the clone that started it all. It was built as a head-to-head benchmark between Claude Opus 4.6 and GPT-5.3-Codex. Claude's version covered 97% of Harvest's features. Codex's version was functional but architecturally compromised. I'm using Claude's version daily.

Claude's Harvest clone showing the editable week grid for time entry
Claude's Harvest clone showing the editable week grid for time entry


The Pattern

Every clone follows the same process:

  1. Write (or generate) a requirements document. Be specific about the data model, the views, the workflows.
  2. Hand it to Claude Opus 4.6 with a prompt to build a Dockerized full-stack application.
  3. Walk away. Come back in ~20 minutes to a running app.
  4. Validate and iterate. Test it for a few days alongside the SaaS product.
  5. Cancel the subscription.

Average build time so far: 17.7 minutes. Average cost: a few dollars in API tokens. Combined annual savings: growing daily.

The source code for every clone is available on GitHub. Clone the repo, run docker compose up --build, and see for yourself.