30/30 platform milestone map
These are the 30 major capabilities behind the marketing-as-a-service offer. Some are ready as public journeys, some are operator-assisted, and some are dependency-gated until live providers and production credentials are attached.
30
major capabilities documented publicly
5
platform categories with conversion paths
4
readiness labels for honest rollout status
Self-hosted foundation
The services that make the platform deployable, observable, and configurable before campaigns scale.
A single-server deployment path for Postgres, SurrealDB, Redis, NATS, Keycloak, MinIO, Bugsink, n8n, Caddy, and related services.
Used as the local and Contabo deployment base while production dependency gates continue tightening.
A public reverse-proxy layer for web, API, service, and workspace routes with automatic TLS as domains come online.
Documented in deployment and security pages as the public entry point for hosted workspaces.
Self-hosted identity with bearer-token APIs, dashboard session protection, and multi-channel MFA/OTP workflows.
Protected dashboard routes, forged-cookie rejection, OTP controllers, and Keycloak setup scripts are present.
Event subjects and realtime update paths for campaigns, commerce, logistics, support, and proof timelines.
Production mode requires a real NATS connection; local mode can fall back while services catch up.
Relational, graph/document, and cache/session storage for campaigns, customer records, operations, and reporting.
Production runtime gates check database health before the main API is allowed to run.
Bugsink, Lighthouse CI, n8n, MinIO, mail, and workspace services support operational visibility and content production.
The public security page positions these as part of the self-hosted trust story.
Operating services
The APIs and service boundaries that connect campaigns to sellers, payments, fulfillment, support, and proof.
Create, track, and report campaigns with readiness, conversion, seller, and profitability context.
Campaign API contracts, campaign services, and campaign Drogon boundaries exist as the execution surface expands.
Build campaign pages, capture leads, attach offers, and route custom domains for launch pages.
Landing page APIs, domain services, frontend routes, and public CTAs are already wired.
Referral links, loyalty balances, transaction visibility, coupons, and tracked seller incentives.
Referral, wallet, coupon, and commerce contracts cover the tracked incentive model.
Acquisition, activation, retention, revenue, referral, and viral events are treated as campaign operating stages.
AAARRR endpoints and contracts are present, and public copy explains the lifecycle loop.
Brand documents, campaign source material, and searchable evidence feed content, support, and AI review workflows.
Knowledge base controllers and docs describe DB-backed search and Ollama embedding support.
Publish thinking, playbooks, launch notes, and proof content as the public authority surface grows.
The public blog now has detail routes while backend publishing continues to mature.
Plan posts, store media assets, review calendars, and prepare publishing handoffs for campaign channels.
Social media controller and content calendar routes exist, with OAuth and live publishing still provider-gated.
Payment links, provider status, checkout, refunds, commissions, payouts, orders, and revenue proof.
Commerce and payment contracts cover provider visibility, order state, coupon impact, commissions, and payouts.
Pop-ups, events, lead capture, check-ins, quick sales, teams, and offline-ready activation workflows.
On-site, POS, and retail activation APIs support event-led selling and proof collection.
Tickets, conversations, call logging, AI voice config, assignment, recovery, and post-purchase care.
Support and contact-center routes are protected and covered by logged-out boundary checks.
RTMP streams, product links, purchase tracking, escrow context, and livestream campaign proof.
Live stream controllers and contracts model stream keys, product linking, and purchase handoffs.
SMS, voice, email, WhatsApp, Telegram, RCS, and authenticator workflows for account and customer verification.
MFA services and actor-based OTP processing are implemented with production dependency checks.
Products, SKU/barcode search, stock readiness, reservations, supplier visibility, handoffs, and campaign risk checks.
Product, warehouse, logistics, and readiness boundaries exist for tying demand to stock reality.
Provider webhooks, fulfillment status, delivery handoffs, returns, refunds, and post-purchase updates.
Logistics services and integration copy expose provider webhooks and delivery event contracts.
Wallet balances, token conversion, virtual cards, Apple Pay/Google Pay compatibility routes, and payout context.
Wallet and card routes exist, with card issuing dependent on provider credentials and compliance.
Public and role surfaces
The pages, dashboards, role apps, and conversion paths that make the platform usable by each audience.
Homepage, services, pricing, operations, integrations, security, contact, personas, sitemap, and robots.
Logged-out Playwright coverage checks the public conversion surface and protected-route boundaries.
Campaigns, agents, analytics, blog, personas, inventory, landing pages, loyalty, referrals, support, cards, settings, and workflows.
Dashboard routes exist behind session checks while authenticated coverage depends on the live auth stack.
Focused pages for brands, founders, marketing teams, creators, sales reps, contact agents, activation teams, partners, operators, developers, career branding, and content/PR teams.
The persona catalog drives public routes and sitemap generation.
Admin, partner, sales, activations, mobile, and shared token packages keep platform roles visually and operationally separate.
The monorepo includes role apps and shared design tokens, with shared UI packages as the next hardening phase.
Operator-assisted automation
The agent, media, and model-runtime milestones that speed up campaign production with human review.
Competitive research, market context, framework analysis, positioning inputs, and evidence-backed strategy drafts.
Agent-service routes and docs cover brand research workflows with model catalog support.
Strategy, content, campaign drafts, media plans, review gates, scheduling, and human approval paths.
Agent workflows, production store, and content operators support draft-to-review campaign production.
C++ media jobs with Ollama, AllTalk, fal.ai, ffmpeg assembly, voice cloning, RSS, and MinIO output paths.
Podcast and documentary contract tests submit jobs and verify status contracts.
Model requirements, local-first inference, provider fallback, and GPU-heavy routing for multimodal work.
Model catalog APIs and provider capability records expose what must be configured before automation runs.
Proof and quality gates
The contracts, audits, and health checks that keep feature claims tied to verifiable behavior.
Generated endpoint sweeps, explicit API contracts, frontend/backend drift audits, backend stub audits, Playwright, Maestro, and Contabo health scripts.
Current local audits report 68/68 frontend-backend matches and 512/512 generated endpoint behavior coverage.
Start with the public-offer and platform-backed pieces, then add operator-assisted and dependency-gated capabilities as credentials, providers, and workflows are ready.