Most products run fine as one project. When you have several teams, heavy traffic or parts that must scale on their own, split them into microservices that talk through signed calls and Kafka events. Same platform, same prompts, nothing to rewrite.
Signed calls, Kafka events and one sign-in between projects
When you have several teams, heavy traffic or parts that must scale on their own, split them into microservices that talk through signed calls and Kafka events. Same platform, same prompts, nothing to rewrite.
Hand-written webhooks with no signature, retry or idempotency; a message broker to wire yourself.
Publish with one line of code. Listen by adding a Kafka item with a topic and an event.
One server and one database. Right for shops, booking sites, internal tools and most apps.
Shop, CRM, accounting and warehouse become separate projects, each with its own server and database, each scaled on its own.
Choose it when you have several teams, heavy traffic, or parts that must deploy and scale separately. Setup guides for Kafka and multi-service come with the prompts.
Every call carries an HMAC signature that is valid for five minutes and only once. A project accepts calls only from the projects you list, and runs them as the user you choose.
Every change between projects carries an idempotency key. A call or an event that arrives again returns the first result instead of charging, mailing or shipping a second time.
Calls to other projects leave through the queue and are retried after 10 s, 1 min, 5 min, 15 min and 1 hour. A project that is down for a while misses nothing.
Publish with one line of code. Listen by adding a Kafka item with a topic and an event. The Kafka controller routes every message, skips duplicates, retries and dead-letters by itself.
People sign in once on your Auth project and are signed in everywhere, with a normal session on each project. Sign out anywhere and you are signed out everywhere. The mobile app gets short-lived signed tokens.
Indexes are declared together with the table and created on import. Every prompt forbids full-table scans, N+1 queries and deep paging, and pages that many people read are cached and refresh themselves when their data changes.
The engine runs on Laravel 13 and PHP 8.3+, with Redis for cache, sessions and the queue, Supervisor for the workers and one cron line for every scheduled job.
Turn on the Octane worker (FrankenPHP) and every /api/view call is answered by an app already loaded in memory. Website, admin and checkout stay on PHP-FPM; one Nginx block turns it off again.
From $59, lifetime. Free updates. Unlimited projects on your own server.