# Build brief — a focused alternative to Systeme.io

> **Verdict:** Partly, if you narrow it · **Buildability:** 51/100 · **Category:** Creator Commerce
> **Source:** https://www.canitbevibecoded.com/systeme-io
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Systeme.io. Verify current pricing and capabilities before acting.

## Context

**Systeme.io** — Bundled funnel builder, email marketing, course hosting, checkout and affiliate program for solo online businesses. It currently costs $17/mo.

None of the individual pieces here are hard: a landing page, an opt-in form, a contacts table, a Stripe checkout, a gated video page, a ref-code cookie. An agent can wire all of that into one self-hosted app in a focused implementation and you will own the list outright. What you cannot one-shot is the boring operational layer: domain authentication, bounce and complaint handling, unsubscribe compliance, and the fact that sending 20,000 emails from your own setup means you now care about deliverability as a personal hobby. You also lose the drag-and-drop editor, which sounds cosmetic until you want to change a headline at 11pm without opening an editor. Verdict lands at kinda because the value survives the rebuild but the maintenance does not disappear.

This brief describes a focused, single-operator replacement for the part of Systeme.io that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Serves your funnel and course pages, captures opt-ins into a local database, sells access through Stripe Checkout, and drips emails plus tracks affiliate referrals from a cron worker.

- Sell digital products from your own pages with payments handled by a provider.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Transactional email provider with a verified sending domain, for example Resend or SES.
- A VPS or serverless host plus your own domain.
- Video hosting for course content, or accept large local files.
- Willingness to handle unsubscribe and bounce logic yourself.

### Data and integrations

- Stripe account for checkout and webhooks.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build a self-hosted, single-operator funnel and course platform. One person runs it, no multi-tenancy.

Stack, no substitutions:
- Next.js 15, App Router, TypeScript, Tailwind
- SQLite via better-sqlite3, single file at ./data/app.db, migrations as plain SQL in ./migrations
- Stripe Checkout plus webhooks for payments
- Resend for outbound email
- No auth provider: magic-link email login for buyers, single admin password from .env

What to build:
1. Funnel pages defined as MDX files in ./content/pages. Each has frontmatter: slug, title, headline, subhead, cta, optional priceId. Render server-side with a clean default layout.
2. Opt-in form component posting to /api/optin. Store contacts in SQLite: email, name, tags, source page, created_at, unsubscribed_at. Double opt-in optional via env flag.
3. Email engine: broadcasts and sequences. A sequence is a JSON file in ./content/sequences with steps (delay in hours, subject, MDX body). A worker script (npm run worker) runs every minute via node-cron, sends due steps through Resend, logs every send in an email_events table. Every email gets a one-click unsubscribe link with a signed token, and List-Unsubscribe headers.
4. Checkout: /api/checkout creates a Stripe Checkout Session for a given priceId. Webhook handler grants a course entitlement on checkout.session.completed, and revokes on refund.
5. Course area at /learn: modules and lessons from MDX in ./content/course, gated by entitlement, video via an embed URL field. Track lesson completion per contact.
6. Affiliate tracking: /r/CODE sets a 60 day first-party cookie, attributes the sale on webhook, writes rows to a commissions table with status pending. Admin page lists commissions. No payouts.
7. Admin at /admin behind the env password: contacts list with search, broadcast composer with a test-send, sales list, commissions list, CSV export of contacts and sales.

Out of scope, do not build: drag-and-drop editors, webinars, blog CMS, tax handling, affiliate payouts, IP warmup, analytics beyond page-view counts stored locally.

Rules: all secrets in .env (STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, RESEND_API_KEY, ADMIN_PASSWORD, APP_URL). No telemetry, no external analytics. Seed the database with two demo contacts, one demo course and one demo sequence so npm run dev shows a working funnel immediately. Include a README with setup steps, a Stripe CLI webhook command, and a deploy note for a single VPS with a persistent volume.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Visual page and email editors, plus the template library that makes launching a funnel a copy-paste job.
- Managed deliverability: shared sending reputation, bounce suppression, spam complaint handling.
- Affiliate program plumbing at the level people expect, including payouts and dashboards for your affiliates.
- Webinars, blogs, and the odd extras that come free in the bundle.
- One vendor to blame when checkout breaks on launch day.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: medium. No reviewed project implementation is linked yet.

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/systeme-io