Comapi VS ShipAnvil

ShipAnvil's answer:

Almost every SaaS starter kit is JavaScript: Next.js, Remix, SvelteKit. ShipAnvil is Symfony, and it is built the way a Symfony team would actually build: Doctrine entities, the security component, Messenger, Twig, and no Node.js anywhere in the build (Tailwind runs standalone, assets go through AssetMapper). Two payment providers, Stripe and Lemon Squeezy, sit behind one interface, so switching is a config change rather than a rewrite. And it ships with EU e-invoicing (Factur-X / EN 16931) already wired, which is a European problem that American kits do not solve.

ShipAnvil's answer:

If you write PHP, the honest answer is stack: a JavaScript kit means learning someone else's ecosystem before you write a line of your own product. Beyond that, three things. It targets Symfony 7.4 LTS, supported until 2029, so a kit bought once does not force a major upgrade six months later. Both payment providers are implemented, not just documented. And the parts people usually postpone are already there and tested: two-factor, webhook replay protection, team roles, an admin with MRR and churn, EU e-invoicing.

ShipAnvil's answer:

Developers who already write PHP and Symfony and are starting a product of their own: solo founders, freelancers building a SaaS on the side, and small agencies who ship client products on Symfony and want a base they can reuse. It assumes you are comfortable with Doctrine, Twig and a terminal. It is not a no-code builder, and it is not for people looking for a hosted platform.

ShipAnvil's answer:

It came out of starting the same project too many times. Every new Symfony product began with the same six weeks before anything specific got written: sign-in and two-factor, billing and the webhook edge cases, teams and roles, an admin with the numbers you actually watch, transactional email, deployment. None of it is the product, all of it has to be right, and getting webhook replay protection or tenant isolation wrong is the kind of mistake you find out about late. So that groundwork was extracted, hardened, tested and documented, and it is now sold as a kit rather than rebuilt each time.

ShipAnvil's answer:

Symfony 7.4 LTS on PHP 8.4 or 8.5, with Doctrine ORM and PostgreSQL 16+. The front end is Twig with Turbo and Stimulus, assets through AssetMapper, and Tailwind v4 in its standalone binary, so there is no Node.js and no bundler in the build. Payments go to Stripe and Lemon Squeezy, e-invoicing follows Factur-X and EN 16931, and the optional AI module talks to the Claude API with streaming and tool use. It ships as a multi-stage Docker image, with a recipe for a plain VPS.