One folder, one bounded contextLLM view

Platform services

What I think: yes to all seven, but write very little ourselves. Build billing's thin core and the flag glue. Fork two. Run three open-source ones as they are. All sit behind kernel ports, so each can be swapped. FROM DOCS + MEASURED licences; efforts and costs are REASONED.

The verdicts

Verdicts are REASONED. Licences are MEASURED in each repository.

ServiceVerdictLicence
Authfork Logto, thinMPL-2.0 plus Logto's own terms (lawyer)
Billingbuild a thin engine; Stripe and the app stores move the moneyours
Customer supportself-host Libredesk now; build laterAGPL-3.0, unmodified
Marketingself-host listmonkAGPL-3.0, unmodified
Analyticsfork Umami, not PlausibleMIT
Voting and feedbackself-host FiderAGPL-3.0, unmodified
Feature flags, front and backOpenFeature with flagd files, inside the app; build the generator and a Dart providerApache-2.0

Effort and cost

REASONED estimates.

ServiceFirst, person-daysEach year, person-daysRunning, USD a month
Auth6 to 9150 more than Logto today
Billing35 to 4515 to 20about 1 per product, plus provider fees
Customer support4 to 63 to 5about 1.5 per product
Marketing5 to 73 to 5about 1 per product, plus email sending
Analytics10 to 148 to 12about 3 per product
Voting and feedback4 to 62 to 4about 1 per product
Feature flags9 to 123 to 50

How each sits

ServiceIn the kernelOutside the app
Autha port in front of the issuerthe fork
Billingnothing: a context says needs: [billing.v1]a shared service
Customer supporta port, the context taga shared service
Marketinga port, the segmentsa shared service
Analyticsa port, the declared eventsa shared service
Voting and feedbacka port, the context taga shared service
Feature flagsthe whole enginenothing
  • Costs are pod memory only. Database slices are not priced.
  • For 20 products: about 150 dollars a month for all seven, before database and provider fees. REASONED.

Why not the names you mentioned

  • Lago: Ruby, which is ruled out, and its free and paid line is unclear.
  • Chatwoot: Ruby. Its core is MIT, with a paid enterprise folder.
  • Plausible: AGPL, Elixir, and funnels are in a folder with no licence to use. Umami is MIT, TypeScript, Postgres only, and has funnels.
  • Canny: hosted only, from 79 dollars a month.

Can we build our own auth service from Logto?

  • Yes, as a thin fork. Subject to the licence check below.
  • Not a rewrite. Writing an issuer is 120+ days and a standing security risk.
  • The price is upkeep: upstream made 1,496 commits, 15 releases and 99 migration files in 12 months. MEASURED.
  • A lawyer must read Logto's terms §2.2 and §3.3 against MPL-2.0 first. The fallback is Logto's paid self-hosted plan, 249 dollars a month for each deployment; how many we would need was NOT CHECKED.
  • Keep our own logic outside it: mailer, first screen, operator.

Build order

  1. Flags: the context switch needs them.
  2. The auth fork's image, while the lawyer reads.
  3. Analytics, then feedback.
  4. Support at the first customers, marketing at the first launch.
  5. Billing before the first paid product. All ports and declaration files exist from day 0, with empty adapters.

Where each one sits

Explorer
  • the engine itself, in the app
  • port; the issuer is the Logto fork
  • port; listmonk behind it
  • port; the Umami fork behind it
  • port; Fider behind it
  • port; Libredesk behind it
  • context.yamlneeds billing.v1, a shared service
  • flags.yaml
  • segments.yaml
  • events.yaml