Technology serving the product
Choose a foundation your teams can evolve
PartITech develops and maintains web platforms, business applications, editorial systems and mobile products across several ecosystems. We select technologies according to use cases, data, integrations, security and operating conditions.
A stack is not a collection of logos. Each component must have an explicit role, a viable community or support model, a clear upgrade path and a maintenance cost consistent with the product.
- Context first
- Needs and risks come before the framework
- Controlled open source
- Dependencies are selected, monitored and documented
- Portability
- A foundation another team can operate and take over
Complementary fields
From business requirements to operations
We combine components suited to each product layer instead of imposing the same architecture on every project.
Back end and business logic
PHP, Symfony and Sonata for business applications, portals, APIs, processing and complex back offices. We use Node.js when its event-driven model genuinely fits the project’s flows.
Symfony & Sonata expertiseCMS and editorial platforms
Drupal for demanding content models, permissions and workflows. WordPress for more direct editorial platforms, with custom blocks and themes. Magento remains part of some legacy e-commerce projects.
Front end and mobile
HTML, CSS, JavaScript and TypeScript form the foundation. React, Vue or Angular structure interfaces when justified. For mobile products, the choice is between native, React Native, Flutter, PWA or Capacitor.
Data, infrastructure and AI
PostgreSQL, Docker containers and Kubernetes orchestration support applications when the context calls for them. Python, LLMs and RAG architectures are integrated within scopes where data, security and evaluation are properly framed.
Discover our AI approachA non-exhaustive selection
Technologies encountered in our projects
Their presence here does not make them interchangeable. We use, maintain or evolve them according to the context.
Symfony
Business applications, APIs and PHP architectures.
Sonata
Back offices and content management within Symfony.
Drupal
Structured and governed content platforms.
WordPress
Editorial sites and custom blocks.
Node.js
APIs, real-time features and event-driven services.
React
Composable interfaces and interactive applications.
Vue.js
Progressive interfaces and web applications.
Angular
An integrated framework for structured front-end applications.
Magento
Taking over and evolving existing e-commerce platforms.
Existing projects
jQuery
Maintenance and gradual modernisation of legacy interfaces.
LegacyA reasoned decision
What we assess before selecting a technology
The choice must remain understandable to the teams that will fund, operate and evolve the product. We compare scenarios instead of presenting a preference as the obvious answer.
Business fit
Domain complexity, workflows, volumes, real time and regulatory constraints.
Expected experience
SEO, accessibility, rendering, native features, offline use and target devices.
Ecosystem
Maturity, documentation, maintenance, available skills and dependencies.
Operations
Deployment, observability, backups, security, load and incident recovery.
Total cost
Build, hosting, potential licences, upgrades and technical debt.
Road map
Support lifetime, compatibility, portability and future migration capability.
From requirements to a validated foundation
Our technology selection method
We reduce uncertainty before committing to the entire implementation.
- 01
Frame the constraints
Use cases, data, integrations, team, schedule, security and operations.
- 02
Audit the existing system
Architecture, versions, dependencies, skills and costs already committed.
- 03
Compare scenarios
Benefits, limitations, risks, transition effort and total cost.
- 04
Test the main risk
A focused prototype addressing performance, integration or the most uncertain feature.
- 05
Document the decision
Target architecture, responsibilities, contribution rules and version road map.
- 06
Industrialise
Environments, tests, delivery, observability and handover to the teams.
Your architecture
Choose a technology for the right reasons
New build, redesign or takeover of an existing system: we can compare the options and make the trade-offs explicit before development begins.