E-commerce
B2C and B2B stores, migrations, integrations and operations.
Technologies
Technologies: the languages, frameworks and platforms we use for your projects
We choose the technology for your project, not the other way round. Magento, Laravel, Symfony, Node.js, React, Next.js, Vue.js, WordPress, Swift, Kotlin, MySQL, AWS, Azure: here is what our teams use every day, and how we decide.
Proven technologies, chosen to last
Our stack, domain by domain
Every technology below is one we deploy and maintain for clients. Click a name to open the page that describes it.
Back-end & APIs
Business applications, APIs and integrations between your tools.
Front-end
Fast, accessible web interfaces that are easy to evolve.
CMS & websites
Corporate and editorial websites, managed by your teams.
Mobile
iOS and Android applications, native or cross-platform.
Data & search
Databases, caching and search engines behind your applications.
Cloud & DevOps
Hosting, repeatable deployments and monitoring.
Integrations & AI
Payments, ERP, PIM, CRM and artificial intelligence connected to your tools.
The technology serves the project, not the other way round.
A good stack is one your teams can operate, your budget can sustain and another team could take over. That is why we compare before we recommend, and why we keep versions, security and documentation current once the project is live.
Choosing out of habit
- A technology imposed because it is the only one known
- A fashionable framework with no team to maintain it
- Code locked in at the provider
- Versions never updated
- Patched-together integrations with no monitoring
The AXELITES choice
- A technology chosen for your project, your team and your budget
- Proven tools we use every day
- Code, documentation and access that belong to you
- Versions tracked and updated under maintenance
- Integrations built to last and monitored
Which technology for which project?
Our usual starting points by project type. The final choice always depends on your catalogue, your tools and your team.
Swipe to see more
| Project | Our usual choices | Why | Dedicated page |
|---|---|---|---|
| E-commerce store | Magento (Open Source, Adobe Commerce, MageOS), Shopify, PrestaShop | Catalogue, B2B and integrations for Magento; fast launch for Shopify; controlled budget for PrestaShop | E-commerce website |
| Corporate website | WordPress, Drupal, Next.js | Content managed by your teams, performance and search visibility | Corporate website |
| Business application | Laravel or Symfony, React, Vue.js or Next.js | Business rules, access rights, APIs and maintainability | Custom applications |
| Mobile application | Swift, Kotlin, React Native, Flutter | Native when usage demands it, cross-platform to share code | Mobile applications |
| Integrations & APIs | REST and GraphQL APIs, ERP, PIM, CRM connectors, Stripe | Reliable flows between your tools, monitored and documented | ERP integration |
| Hosting & operations | AWS, Azure, CI/CD, Cloudflare | Repeatable environments, backups and monitoring | Hosting and managed services |
Already have a stack? We audit it before recommending anything: a technology that works and that your team knows is often worth keeping. Discuss your project
How we move forward together
Understand
Your need, the existing systems, your tools and your team’s skills: the technical choice starts there, not with a catalogue of frameworks.
Compare
Functional coverage, integrations, licensing and hosting costs, maintenance and skill availability are compared side by side.
Prototype when needed
A technical uncertainty is resolved on a small scope before committing to the project, not after.
Decide and document
The choice is argued in writing, the architecture documented and the maintenance plan defined with you.
A technical choice argued, documented and maintained over time.
Over time
A technology is chosen, then looked after.
An outdated framework becomes a security risk and a brake on improvements. We track the versions of the technologies we deploy and keep them current under maintenance, with regular reporting.
- Framework and CMS versions tracked
- Security patches applied and recorded
- Dependencies checked at every release
- Code and documentation that belong to you
Technology sheets
What each technology is for, where it fits in an architecture and when we recommend it.
Angular for business web applications
Structure an Angular application around interfaces, forms, navigation and connections to your business services.
Read the sheet
AWS for application hosting and operation
Prepare AWS architecture, deployment, permissions, backups and resource follow-up for your applications.
Read the sheet
Laravel for custom web applications
Build a Laravel application with structured business rules, APIs, coherent data and a prepared maintenance approach.
Read the sheet
Magento as an e-commerce technology
Understand Magento’s catalogue, store management, extensions and integration needs before building or evolving an online store.
Read the sheet
Microsoft Azure for your cloud infrastructure
Organise Azure hosting around applications, connections, permissions, deployments, data and operational follow-up.
Read the sheet
MySQL for application data
Structure and develop a MySQL database with relational models, queries, permissions, backups and data recovery arrangements.
Read the sheet
Next.js development for your web applications
Build websites, portals and web applications with Next.js: React interfaces, rendering suited to your content and connections to your business tools.
Read the sheet
PHP for web applications and services
PHP development and takeover for business rules, APIs, data access, dependencies and web application performance.
Read the sheet
React for evolving web interfaces
Build or improve a React interface with clear components, data flows, interactions and API connections.
Read the sheet
SQL Server for enterprise data
Design and improve SQL Server databases with data models, queries, permissions, backups and application integration.
Read the sheet
Symfony for structured business applications
Develop or take over a Symfony application with clear modules, data access, permissions and maintainable business processing.
Read the sheet
Vue.js for interactive web interfaces
Build a Vue.js interface or improve an existing screen through components, reactive data and carefully scoped integration.
Read the sheet
WordPress CMS for your websites and content
Create or develop a WordPress website with organised content, themes, extensions, search foundations and maintenance.
Read the sheetYour questions, our answers
Practical answers to help you make the right decisions before starting your project.
Discuss my projectBecause every project has its own constraints: catalogue, integrations, in-house team, budget and deadlines. A store with a complex catalogue, a corporate website and a business application do not call for the same answer. We choose among the technologies we use every day, compare the options and explain the choice in writing.
Often, yes. We start with an audit of the code, dependencies and hosting to assess the takeover. If the technology is proven and maintained, we assemble the right team; otherwise we propose a gradual modernization plan rather than a complete rewrite.
You do. The source code, documentation and access belong to you. Every architecture choice is documented so another team can take over the project if you wish, and versions are tracked under maintenance.
Let’s talk about the right technology for your project
Describe your need, your existing tools and your team: we will propose a reasoned choice and a first estimate.