Flow Mesh — Commercialization Plan

Living document. Updated as pricing decisions are made. Related: DISTRO.md (distribution channels), bead flow-mesh-19d


1. Positioning

Flow Mesh is a self-hosted bidirectional work sync engine for humans and AI agents.

Category: Developer infrastructure / Work orchestration Comparable products: n8n, Cal.com, Plausible, Gitea, Linear (self-hosted alternative) Differentiator: Agent-first CLI + intelligence layer + bidirectional sync (not just one-way Zapier pipes)

One-liner: "The sync engine that lets AI agents manage your work across Asana, Discord, and Git."


2. Pricing Model: 14-Day Trial + License Key

Every download starts a 14-day Pro trial, no key needed. When the trial ends the install locks: no free tier. Buy once, activate with one command.

Tiers (launch deal vs anchoring price)

Tier Launch deal Anchoring price Billing
Pro $497 $1,497 Lifetime one-time, or $390/yr
Team $997 $2,997 Lifetime one-time, or $990/yr
Enterprise Contact Contact Annual contract

Launch deals are limited lifetime licenses. When they run out, prices revert to the anchoring price.

Feature Matrix

Feature Pro Team Enterprise
Sync Engine
Meshes ∞ ∞ ∞
Asana + Discord + Beads/Git ✓ ✓ ✓
Event ledger (30 types) ✓ ✓ ✓
Conflict detection + resolution ✓ ✓ ✓
Loop guard + fingerprint dedup ✓ ✓ ✓
Policy engine (templates A/B/C) ✓ ✓ ✓
Drift detection ✓ ✓ ✓
Auto drift repair ✓ ✓ ✓
UI & CLI
Web UI (dark theme, mobile) ✓ ✓ ✓
CLI with --format json ✓ ✓ ✓
mesh bootstrap ✓ ✓ ✓
Users & Auth
Users 1 5 ∞
Basic auth (bcrypt + cookies) ✓ ✓ ✓
API token (Bearer) ✓ ✓ ✓
SSO / LDAP / SAML ✗ ✗ ✓
Intelligence
AI intelligence layer ✓ ✓ ✓
Natural language task management ✓ ✓ ✓
Project planning + decomposition ✓ ✓ ✓
Coding delegation (pi) ✗ ✓ ✓
Voice transcription ✓ ✓ ✓
Brainstorm module ✓ ✓ ✓
Scheduled jobs (standup, alerts) ✗ ✓ ✓
Memory (MEMORY.md persistence) ✓ ✓ ✓
Spending limits + tracking ✓ ✓ ✓
Agent Integration
MCP gateway ✓ ✓ ✓
Auto-mesh (folder watching) ✓ ✓ ✓
Export (events, snapshot) ✗ ✓ ✓
Email transport ✗ ✓ ✓
Providers
Asana ✓ ✓ ✓
Discord ✓ ✓ ✓
Beads / Git ✓ ✓ ✓
GitHub Issues ✓ ✓ ✓
Slack ✓ ✓ ✓
Linear ✗ ✓ ✓
Custom providers ✗ ✗ ✓
Support
Direct support ✓ ✓ ✓
Priority GitHub Issues ✓ ✓ ✓
Direct support (email/Discord) ✗ ✓ ✓
SLA ✗ ✗ ✓
Onboarding call ✗ ✗ ✓

UI Manifestation of Tiers

Every gate must be visible in the web UI (see UI.md §8):

  • Free: Sees 3 mesh cards max. "Upgrade" banner when limit hit. No chat widget. No intelligence page.
  • Pro: Unlimited meshes. Chat widget on every page. Intelligence page. Export buttons.
  • Team: Pro + delegation panel. Scheduled jobs config. Analytics dashboard.
  • Enterprise: Full admin panel. User management. SSO config.

Upgrade prompts are inline banners, never modal popups.

Why These Gates

Gate Rationale
3 mesh limit Generous for solo devs. Natural upgrade: "I need a 4th project."
Intelligence = Pro Highest-value feature. Uses user's own API keys (zero cost to us). Natural "wow" moment.
MCP = Pro Agent users are power users → willing to pay.
Delegation = Team Spawning pi sessions = heavy usage pattern → higher tier.
Scheduled jobs = Team Automated workflows = team/agency use case.
Export = Team Data portability for professional use.
Additional providers = Pro/Team Core 3 (Asana/Discord/Beads) free. GitHub/Slack/Linear = professional need.

3. License Key System

Design Principles

  • Offline validation — no phone-home. Respects self-hosted ethos.
  • Signed JWT — contains tier, expiry, mesh limit, user limit.
  • Grace period — 30 days after expiry. No hostage-taking.
  • Lock, not linger — expired trial with no key locks mesh creation. Paid keys keep a 30-day grace period after expiry.

Key Format

FM-PRO-XXXX-XXXX-XXXX-XXXX
FM-TEAM-XXXX-XXXX-XXXX-XXXX
FM-ENT-XXXX-XXXX-XXXX-XXXX

Activation Flow

# Purchase → receive key via email
# Activate
mesh license activate FM-PRO-XXXX-XXXX-XXXX-XXXX

# Check status
mesh license status
# Tier: Pro
# Meshes: unlimited
# Users: 1
# Expires: 2027-02-24
# Status: active

# Deactivate (move to another server)
mesh license deactivate

Implementation

// License is a signed JWT
type License struct {
    Tier       string    `json:"tier"`       // community, pro, team, enterprise
    MeshLimit  int       `json:"meshes"`     // -1 = unlimited
    UserLimit  int       `json:"users"`      // -1 = unlimited
    Features   []string  `json:"features"`   // explicit feature flags
    IssuedAt   time.Time `json:"iat"`
    ExpiresAt  time.Time `json:"exp"`
    CustomerID string    `json:"cid"`        // for support lookup
}

// Signed with Ed25519 key pair
// Public key embedded in binary → offline validation
// Private key held by us → key generation

Feature Gating (in code)

// Check before enabling a feature
if !license.HasFeature("intelligence") {
    return errors.New("intelligence requires Pro license — mesh license activate FM-PRO-...")
}

// Check mesh limit
if license.MeshLimit > 0 && currentMeshCount >= license.MeshLimit {
    return fmt.Errorf("mesh limit reached (%d) — upgrade at flowme.sh/pricing", license.MeshLimit)
}

Anti-Piracy (Minimal)

We're a developer tool — heavy DRM is counterproductive.

  • Ed25519 signature prevents key forgery
  • No phone-home, no hardware fingerprint
  • If someone cracks it, they weren't going to pay anyway
  • Focus on making paying easy, not pirating hard

4. Payment System

Stripe Checkout

flowme.sh/pricing → Select tier → Stripe Checkout → License key emailed
Component Implementation
Landing page Static site at flowme.sh
Pricing page flowme.sh/pricing
Checkout Stripe Checkout (hosted)
Key delivery Stripe webhook → generate JWT → email via Resend/Postmark
Portal Stripe Customer Portal for subscription management
Receipts Stripe automatic receipts

Stripe Products

prod_flowmesh_pro       → $19/mo or $180/yr
prod_flowmesh_team      → $49/mo or $480/yr
prod_flowmesh_enterprise → custom (manual invoice)

Key Generation Service

Lightweight Go service (or Lambda) that:

  1. Receives Stripe checkout.session.completed webhook
  2. Generates signed JWT license key
  3. Emails key to customer
  4. Stores in DB for support/revocation

Can run on the same server as flowme.sh or as a Cloudflare Worker.


5. Domain & Web Presence

URL Purpose
flowme.sh Landing page + pricing + install instructions
docs.flowme.sh Mintlify documentation (69 pages)
app.flowme.sh Demo instance (optional, future)
api.flowme.sh License key API (optional, could be on main)
github.com/Philoveracity/flow-mesh Source code (public)

Landing Page Sections

  1. Hero — "The sync engine for humans and AI agents"
  2. Demo GIF / video — 30-second mesh creation
  3. Feature grid — 6 cards
  4. Pricing table — 4 tiers
  5. Install command — curl -fsSL flowme.sh/install | sh
  6. Testimonials (later)
  7. Footer — GitHub, docs, Discord

6. Go-to-Market

Phase 1: Soft Launch (Week 1-2)

  • [ ] Domain: register flowme.sh
  • [ ] Landing page: deploy static site
  • [ ] Mintlify: deploy docs.flowme.sh
  • [x] GitHub: repo stays private (owner decision 2026-09-26)
  • [ ] Install script: verify on 5 platforms
  • [x] License: 14-day Pro trial, no key; expired keyless trial locks (no Community tier)
  • [ ] CHANGELOG: v0.4.0 release

Phase 2: Growth (Week 3-8)

  • [ ] Hacker News: "Show HN: Flow Mesh — bidirectional work sync for AI agents"
  • [ ] Reddit: r/selfhosted, r/devops, r/artificial
  • [ ] Discord: Flow Mesh community server
  • [ ] Twitter/X: Launch thread
  • [ ] YouTube: 5-minute demo video
  • [ ] Blog post: "Why we built Flow Mesh"

Phase 3: Monetization (Week 4-12)

  • [ ] Stripe: set up products + checkout
  • [ ] License key service: deploy
  • [ ] Pro tier: gate intelligence + MCP + auto-mesh
  • [ ] Team tier: gate delegation + scheduled + export
  • [ ] Email: drip campaign for free → Pro conversion
  • [ ] Analytics: PostHog funnels (install → activate → upgrade)

Phase 4: Growth (Month 3+)

  • [ ] Integrations: more providers (Jira, Notion, Trello)
  • [ ] Cloud offering: managed Flow Mesh (higher margin)
  • [ ] Partner program: agencies deploying for clients
  • [ ] Enterprise: direct sales for larger orgs

7. Revenue Projections (Conservative)

Year 1

Metric Month 3 Month 6 Month 12
Downloads 500 2,000 5,000
Active installs 200 800 2,000
Pro subscribers 10 40 100
Team subscribers 2 10 30
MRR $288 $1,250 $3,370
ARR $3,456 $15,000 $40,440

Assumptions

  • 4% free → Pro conversion (industry avg for dev tools: 2-5%)
  • 1% free → Team conversion
  • 10% monthly churn on Pro, 5% on Team
  • No enterprise deals in Year 1

Costs

Item Monthly
Domain (flowme.sh) $3.75
Mintlify (free tier) $0
Stripe fees (2.9% + $0.30) ~$100 at scale
Email (Resend) $0 (free tier)
GitHub (free for public) $0
Server (existing) $0
Total ~$104/mo at scale

Margin: ~97% at $3,370 MRR. Pure software, self-hosted, no cloud infra.


8. License: Closed Source, Paid Licenses

Owner decision 2026-09-26: Flow Mesh stays private closed-source. No open-source license grant, no BSL conversion promise, no timeline. The repository stays private; distribution is licensed binaries through flowme.sh plus a 14-day Pro trial. Possible future: open extensions around a closed core — extensions only, never the core.

  • No free tier. Expired keyless trials lock; mesh creation requires an activated paid key.
  • Trial clock is per user and per directory (earliest start wins), so new folders cannot restart trials.
  • Refunds: 30 days, no questions, on every paid license.

9. Competitive Landscape

Product Self-Hosted Bidirectional Agent-First
Flow Mesh ✓ ✓ ✓
Zapier ✗ ✗ (one-way) ✗
n8n ✓ ✗ (workflow) ✗
Make ✗ ✗ (one-way) ✗
Unito ✗ ✓ ✗
Linear ✗ ✗ (standalone) Partial

Unique value: Self-hosted + bidirectional + agent-first. Nobody else does all three.


10. Open Questions

  • [ ] Annual discount: 21% (2 months free) vs 25% — which converts better?
  • [x] Trial: 14-day Pro trial, no credit card, no key. Expired keyless trial locks.
  • [ ] Education discount: 50% off for .edu emails?
  • [ ] Cloud offering: Managed Flow Mesh (flowme.sh/cloud) — when/if?
  • [ ] CLI-only tier: Cheaper Pro without web UI? (Probably not — too confusing)

Created: 2026-02-24 | Author: AI + Verious Smith

Generated from the Flow Mesh repository by scripts/build-docs-site.sh. If a page is wrong here, the file it was rendered from is wrong.