← All work

Meeks Labs platform

The shared billing, notification, CRM and support services that sit behind every Meeks Labs product.

Meeks Labs platform system diagram

The problem

Every product needs the same unglamorous parts: sign-in, plans and payments, emails and push notifications, a place to track customers, and a way for people to ask for help. Rebuilding them for each app is slow, and it leaves you with five slightly different billing systems to keep correct.

What I built

I built these once, as small services that every Meeks Labs product shares.

  • Billing: a Go service that owns Stripe. Products never build their own checkout. They hand the signed-in user to the billing app with a short-lived, single-use code, so there is no second login. Stripe webhooks, not browser redirects, decide what a customer has paid for. Other products ask billing what a user is entitled to, and answers are cached and refreshed the moment a subscription changes.
  • Notifications: a Go service for email and push. Each message belongs to a category: transactional mail users cannot turn off, product alerts they can, and marketing that respects opt-outs.
  • CRM: a Swift Vapor service for contacts and deals, with access checked against billing before any feature is granted.
  • Support: a Swift Vapor ticket system with a threaded conversation on web and iOS, an inbox for me, and AI-drafted replies.

All of them use one Firebase project for identity, so one account works across everything. Each is deployed as its own container on Google Cloud Run.

Stack

  • Go for billing and notifications, with Stripe and Firebase Cloud Messaging
  • Swift 6 and Vapor 4 with Fluent for the CRM and support services
  • PostgreSQL for each service's data
  • SvelteKit for the billing and web interfaces
  • Firebase Auth, Cloud Run, Cloud Build and Secret Manager

Outcome

New products plug into accounts, subscriptions, notifications, CRM and support instead of rebuilding them. CompStack, Veris and Intelligent Outreach are built on it. For a client, the same approach means a payments and accounts foundation that is built carefully once, tested, and reused.

Have something similar in mind?

Start a project