Architecture, code and cloud
From idea to architecture, from code to cloud.
Designing and modernising demanding software systems: architecture, Java and Spring Boot, Angular, DevOps, cloud and artificial intelligence. A single point of contact, argued decisions, usable deliverables.
Framing and audit within days Documented, transferable deliverables Support for your existing teams
Technical expertise, not a slide deck
Codexway supports organisations that must evolve an existing system without interrupting operations, or build a new platform without accumulating technical debt from day one.
Every engagement starts by understanding the real context: operational constraints, available skills, existing commitments, non-negotiable deadlines. Architectural decisions are then explained, quantified and documented.
Assessment grounded in existing code and infrastructure Architecture decisions traced and justified Knowledge transfer built into the engagement
Modular architecture diagram with nodes and connections
Services
Fifteen ways to engage
From architecture framing to team enablement, each service is described with its method, deliverables and success criteria.
Software architecture and technical framing
I design and review application architectures that match your real team, timeline and operations constraints. You get a reasoned target split into deliverable stages, not a two-hundred-page document.
Architecture and code audit
An independent audit that delivers facts, measurements and a priority order. You know what threatens your system, what it really costs and what to fix first.
Legacy application modernisation
I evolve legacy applications through controlled stages while production stays live. The goal is not to rewrite everything, but to take back control of a system you no longer dare to change.
Java and Spring Boot back-end development
I design and build robust business services with Java and Spring Boot, tested and observable from day one. The delivered code is readable, documented and easy for your team to take over.
Angular front-end development
I build fast, accessible and tested Angular interfaces on a readable codebase. You get measured user journeys, not just screens that render.
Cloud architecture and infrastructure as code
I design reproducible cloud platforms, fully described as code and sized to actual need. You gain control over costs as well as the ability to recover from incidents.
Key facts
Scope of engagement
These figures describe the offering, not client results: they show what can be taken on and how.
6
Areas of expertise
Architecture, development, cloud and DevOps, security, data and AI, consulting and training.
15
Services described
From architecture framing to training, including industrialisation and applied AI.
4
Method steps
Framing, analysis, building in deliverable increments, handover and follow-up.
40+
Technologies in practice
Java and Spring ecosystem, Angular, containerisation, cloud, observability and AI tooling.
3
Engagement formats
Fixed price for bounded deliverables, time and materials for advisory, recurring days for follow-up.
30 min
First conversation
Thirty minutes to qualify your need and tell you honestly whether an engagement is useful.
Method
Four steps, no grey areas
Each step produces a verifiable deliverable. You always know where the engagement stands and what remains to be decided.
- 1
Frame
Interviews, review of existing code and infrastructure, measurement of the current state. Goal: state the real problem and the non-negotiable constraints.
- 2
Design
Architecture proposal, comparison of options, risk and cost analysis, migration plan in deliverable increments.
- 3
Build
Delivery in short batches, code reviews, automated tests, continuous integration and progressive production rollout.
- 4
Transfer
Architecture documentation, operations guides, workshops with your teams and post-release follow-up.
Technologies
A mastered foundation, not a logo wall
Every technology listed is used in production on live systems.
- Java
- TypeScript
- Spring Boot
- Spring Security
- Spring AI
- Angular
- PostgreSQL
- Apache Kafka
- Docker
- Kubernetes
- Terraform
- GitHub Actions
- Argo CD
- Grafana
- OpenTelemetry
- Keycloak
- Testcontainers
- Playwright
- AWS
- Microsoft Azure
Versions are verified for each engagement: a technology is only recommended when it brings measurable benefit to the context.
Case studies
Concrete situations
Monolith modernisation, containerised platform, system integration, delivery chain industrialisation. These demonstration samples illustrate the approach, without referring to any real client.
Incremental overhaul of a contract management monolith
Modernisation through domain extraction, with no service interruption
Demonstration sample - not a real client reference.
Multi-environment Kubernetes platform for a software vendor
A shared foundation for twelve applications and eighty customer instances
Demonstration sample - not a real client reference.
Angular front-end migration and performance overhaul
Five versions behind, one hundred and eighty screens, migrated in shippable batches
Demonstration sample - not a real client reference.
Testimonials
What teams say
Sample testimonials: they illustrate the kind of feedback expected, they do not refer to real clients.
« Starting with a secondary domain let us validate the method without exposing production. The tests written at the beginning now support every release. »
Demonstration sample: this testimonial is fictional and intended to illustrate the kind of feedback expected after an incremental modernisation of a monolithic system.
« The most visible gain is not technical: we can finally prepare a customer environment without a coordination meeting. Documenting the foundation also made onboarding a new engineer much easier. »
Demonstration sample: fictional testimonial illustrating a multi-tenant Kubernetes hosting industrialisation.
« The most tangible change for our teams is being able to see a failed message and replay it ourselves. Before, that always required a developer. »
Demonstration sample: fictional testimonial illustrating taking ownership of an integration foundation between heterogeneous systems.
« We feared a long migration with an unmaintainable branch. Splitting it into batches let us ship every two weeks and keep production stable. »
Demonstration sample: fictional testimonial illustrating an Angular migration delivered in shippable batches.
« Friday evening deployments are gone. We now ship during the day, and rollback no longer requires a crisis meeting. »
Demonstration sample: fictional testimonial illustrating the industrialisation of a delivery pipeline and the move to GitOps.
« What changed how people work is the systematic citation of sources. Our consultants check the document version before reusing a recommendation. »
Demonstration sample: fictional testimonial illustrating the rollout of a document assistant with guardrails.
Insights
Technical deep dives
Architecture, Java and Spring Boot, Angular, DevOps, cloud, security, artificial intelligence: articles documenting real decisions.
Hexagonal architecture with Spring Boot 4: what it really changes
Creating three folders does not make an architecture hexagonal. Here is the dependency rule, the code that respects it, and the tests it finally makes possible with Spring Boot 4 and Java 21.
Signals and zoneless mode in Angular 22: what changes for an existing application
Zoneless mode removes automatic change detection. In practice, that exposes useless renders and forces a rethink of how state moves through the application.
JWT and refresh token rotation: the part we often forget
A short-lived access token is good practice. Without rotation and reuse detection on the refresh side, a stolen token stays exploitable silently for weeks.
FAQ
Questions asked before starting
Duration, pricing, remote work, knowledge transfer, intellectual property: straightforward answers.
How does a typical engagement run?
It starts with a free one-hour framing call to understand your context and check whether an engagement makes sense. If we proceed, you receive a written proposal covering scope, deliverables, schedule and terms. The work then begins with a short analysis phase and continues in deliverable increments, each closed with a demo and a progress review.
How long does an engagement usually last?
An audit or architecture framing typically takes two to eight weeks. Development or industrialisation work usually spans two to six months, part-time or full-time. Ongoing advisory can be limited to one or two days a month and continue over several quarters.
How is pricing set?
Pricing is fixed-price for clearly bounded deliverables, or time and materials for advisory and evolving engagements. The indicative figures shown on this demonstration site are examples only and do not constitute a contractual offer: every proposal is priced after framing, based on scope, duration and urgency.
Do you work remotely?
Yes, most engagements run remotely with regular video checkpoints. I travel for the phases that justify it: framing workshops, architecture reviews, audit restitution and training sessions. Travel is planned in advance and invoiced at cost.
How do you ensure knowledge transfer?
Transfer is built into the engagement rather than added at the end. Technical decisions are explained when they are made, code reviews are collective, and every deliverable comes with usable documentation. On longer engagements I pair with one or two internal developers so they can take over when I leave.
Who owns the produced deliverables?
Code, documentation and deliverables produced specifically for your project belong to you, with rights of use assigned under the contract terms. Methods, templates and generic components created outside the engagement remain their author's property, but their use in your project is guaranteed and documented.
A specific need, an architectural doubt, a decision to clarify?
A first conversation qualifies the need and checks whether an engagement makes sense. If it does not, you still leave with a clear direction.
Contact
Describe your situation
A few lines are enough to start. Reply within one business day.
Thank you, your message has been received. You will get a reply within one business day.