Built every day.
Shipped every week.
Pagayo is a living platform. New features, new modules, new improvements ship continuously — driven by what the people who actually use it ask for. This is a transparent week-by-week log of how the platform grew, and how it keeps growing.
From day one, every change went through a pull request. Every deployment was automated. Every piece of infrastructure was provisioned as code — not because it was the easy path, but because it was the right one.
The result is a platform built on Cloudflare's global edge network: no servers to manage, no downtime windows, no single point of failure. CI/CD from commit one. Automated testing from the start. A codebase built to ship weekly, indefinitely.
The timeline below is not marketing. It is what actually happened — and it keeps getting longer.
The idea becomes code
First commit. One server. One goal: every sales channel in a single platform. No investors, no team — just a vision and an empty repository.
Product catalogue
Products. Categories. A first admin interface. The building blocks of any commerce platform, laid down cleanly from the start.
User authentication
Login, sessions, roles. A storefront without authentication is a demo, not a platform. Security-first from week three.
Customers can pay
First checkout flow. Database. A working end-to-end order. A webshop is not a webshop without a pay button — so that came first.
CI/CD from day one
Automated deployment pipeline. Every push triggers a build, a test run, and a deploy to staging. No manual deployments — ever. This discipline has held for every week since.
API layer introduced
A dedicated API Stack repository. Payment providers, webhooks, and external integrations move out of the storefront into their own service. Clean separation from the start.
Stripe integrated
Real payment intents. Webhook verification. Idempotent event handling. Money flows through the platform reliably for the first time.
BUNQ banking connected
Dutch banking integration live. Payment events forwarded to tenants in real time. The API Stack handles its first multi-provider routing.
Multi-tenant foundation
The most important architectural decision: every customer gets their own fully isolated database and environment. No shared tables. No data mixing. This is what makes Pagayo a platform, not a product.
Shared schema package
@pagayo/schema introduced. One set of database definitions, shared across all repositories. A single source of truth — enforced in code, not in documentation.
Design system extracted
@pagayo/design: tokens, components, and context bundles as a standalone package. Every consumer inherits the same visual language. No local overrides.
Shared configuration
@pagayo/config: domains, endpoints, policy, and runtime defaults in one place. Ten repositories, one source of truth for configuration.
First customer live
A real business on their own subdomain. Real orders. Real payments. The platform works — not just in tests, but in production.
POS channel
Point-of-sale flows added alongside the webshop. Same order model, same pipeline, different input surface. The Order-First architecture proves its value for the first time.
Custom domains
Tenants can connect their own domain. Cloudflare for SaaS provisions SSL and routing automatically. No manual DNS configuration. No per-tenant deploy.
One order model for everything
Webshop, POS, WhatsApp, QR — every sales channel flows into a single Order model with a source and an originator. No channel subtypes. No if/else per channel. Order-First.
Edge Workers — core routes
Phase A of the Cloudflare Workers migration complete. Core storefront routes move from a traditional server to the global edge. No infrastructure. No cold starts.
Edge Workers — admin routes
Phase B complete. Admin panel, settings, and tenant management all running on Workers. The last server dependency starts to disappear.
Edge Workers — payment routes
Phase C complete. The full platform runs on Cloudflare Workers. No servers. No VMs. No orchestration. The migration that was planned in months shipped in weeks.
Database at the edge
The database layer was replaced by Cloudflare D1. Every customer gets their own SQLite database, running alongside the Worker — not in a distant data centre. Latency drops. Complexity drops.
Automatic tenant provisioning
New customer? The platform creates a D1 database, applies the full schema, configures Cloudflare routing, and sets up KV cache — all automatically. No deployment. No manual steps.
Subscriptions and memberships
Recurring billing, member management, and visit tracking. Sports clubs, gyms, and membership organisations get a dedicated flow built into the same platform.
Passkey authentication
Passwordless login via WebAuthn. Customers authenticate with Face ID or fingerprint. No passwords to forget, no credentials to breach.
International payment methods
M-Pesa, Flutterwave, and Paystack added. Nigeria, Ghana, South Africa, Kenya — localised payment methods across Europe and Africa, unified in one API layer.
Data migration tooling
Import pipelines for WooCommerce and Magento. Retailers can move their entire catalogue and order history into Pagayo without manual data entry.
Newsletter and announcements
Built-in newsletter tooling with DNS automation. Social announcements. Tenant-to-customer communication without a third-party dependency.
AI layer introduced
AI configuration, action logging, and insight tracking added to the tenant schema. The groundwork for intelligent commerce features — product descriptions, demand forecasting, search.
Today
2500+ automated deployments. 10 repositories. 59 database tables per tenant. Continuous delivery from the first commit. One developer. Still building.
Got an idea, a question, or a feature you wish existed? Pagayo grows from what the people using it ask for — we'd love to hear from you.
Get in touch →