B2B portals & domain logic
Pricing rules, permissions, approvals and history - a standard CMS hits its limits here quickly.
Backend - Symfony
Symfony for complex domains.
Enterprise PHP, APIs and portals - with clear bundles, tests and a deploy path your team can actually run.
APIs
Portals
DDD-lite
Messenger
PHPUnit
Where Symfony fits
When rules, integrations and lifespan reach further than a seasonal shop.
Legacy systems
Symfony apps that grew without tests and without clear modules. We carve them up instead of reinventing them.
API-first teams
Several frontends, partners and mobile need stable contracts - not one UI that drags everything along.
IT under compliance pressure
Auditable releases, traceable auth and logging belong in the scope, not in an addendum.
What we deliver in Symfony
From the first slice to handover - operations included.
APIs & integrations
REST or messaging to ERP, CRM and line-of-business systems. Contracts, versioning, error paths.
Domain modules
Clear bounded contexts instead of monolithic controllers. Bundles only where they really share something.
Queues & jobs
Messenger, retries, dead-letter - so imports and mail do not block the request.
Quality & CI
PHPUnit, static analysis, staging and review. No “hotfix on prod, we will look tomorrow”.
Approach: architecture before magic
We use Symfony as a tool - not as a religion. Fewer bundles, more explicit modules. What the team cannot explain does not go to production.
- Read the existing code and the risks before stacking features
- Define the slice: modules, auth, deploy, observability
- Deliver iteratively - with tests on the expensive edges
- Handover with docs, runbooks and optional maintenance
How a Symfony project runs
Four steps - from the audit to stable operations.
Read
Code, data flows, pain. Result: a sketch of the slice and the risks, not 80 slides.
Slice
First module or API slice on staging - including auth and test data.
Harden
Observability, jobs, permissions. Performance on the real bottlenecks, not on synthetic micro-benchmarks.
Hand over
Docs, deploy, knowledge transfer. Optional: an SLA through maintenance.
What you can build on
Enterprise-ready - without the overloaded enterprise effort.
Upgradeable
We plan Symfony upgrades as work, not as a surprise three major versions later.
Fits your team
Code your developers can read. No opaque bundles without an owner.
Ongoing care
After go-live: hotfixes, security and releases - in line with our maintenance packages.
Frequently asked questions
Honest - as in the kickoff.
Symfony or Laravel?
Complex domain, long lifespan, several teams: often Symfony. A fast business backend with a small team: often Laravel. We say which one before the first sprint.
Can you lift an old Symfony 3/4?
Yes - step by step. Tests and deploy first, then the components. No big-bang rewrite without evidence.
Flex, bundles, DDD - do we need all of it?
Only what the case carries. DDD-lite where rules are expensive. Bundles are not a status symbol.
Do you take over existing code?
Yes, after a short audit. We name the risks and a realistic slice - even when the answer is “stabilise first”.
What does hosting look like?
We work with your cloud or your hosting provider. We set up containers and CI without infrastructure dogma.
What does it cost to start?
After discovery, a fixed scope for the audit plus the first slice. Details under contact.
More stacks
Related technologies we often use alongside.
Ready for the next Symfony slice?
Describe briefly which portal or which API you need - we come back with a concrete proposal.