Startups
A first version in front of real users, on foundations that will hold.
IT consulting · Software · DevOps · AIWe build your
We build your
One team, from idea to production.
Aggregax is the technology partner for companies that want to move faster without losing control. We advise on your IT strategy, design and build your software, automate your delivery in the cloud and put AI to work on real problems in your business.
- One accountable team
- You own the code
- English and French
Services
Four ways we move your business forward
Take one service or combine them. The same people who advise you can build the product, automate its delivery and add AI where it pays off, so nothing is lost between a slide deck and production.
Senior, hands-on, accountable. The people you meet in the first call are the people who do the work. You get direct access to them, a shared board and a demo at the end of every iteration.
Audit and assessment
We review your architecture, code, infrastructure and running costs, then tell you plainly what is solid, what is fragile and what to fix first.
Roadmap and architecture
A prioritised plan with a target architecture, budget ranges and milestones your teams can actually follow.
Technical leadership on demand
Senior guidance for the decisions that are expensive to get wrong: build or buy, choosing vendors, hiring, security.
Web and mobile applications
From customer portals to internal tools and mobile apps, designed with your users and delivered in short, visible iterations.
APIs, back ends and integrations
Reliable services that connect your product to your ERP, CRM, payment and partner systems.
Modernising legacy software
We replace ageing systems step by step, without stopping the business that depends on them.
Automated delivery pipelines
Every change is built, tested and deployed the same way, so a release becomes a routine event instead of a risky one.
Cloud infrastructure as code
Environments described in code: reproducible, reviewed like any other change, and sized to what you really use.
Monitoring and reliability
Dashboards, alerts and clear runbooks, so problems are seen and handled before your customers notice them.
Assistants on your own knowledge
Chat and search over your documents and data, with answers that cite their sources and respect your access rights.
Automating document-heavy work
Extraction, classification and drafting for the repetitive tasks that slow your teams down, with a person approving what matters.
From prototype to production
We measure quality before launch, monitor it afterwards, and keep cost and data privacy under control.
How we work
From first call to production
Three steps, no surprises. You see working software early, you decide at every stage, and you keep everything we build.
01Discover
Understand before we build
We start with the problem, not the technology.
Workshops with your business and technical people, a look at your existing systems, and a frank conversation about constraints. You leave with a scoped proposal you can compare and challenge.
- Workshops with the people who know the business
- Review of your existing systems and constraints
- A scoped proposal: priorities, budget and timeline
02Build
Deliver in short, visible iterations
Working software every two weeks.
A small senior team designs, builds and tests your product in sprints. Each one ends with a demo on a real environment, so you steer with facts instead of status reports.
- A demo at the end of every sprint
- Automated tests and code review on every change
- A shared board: you always know where things stand
03Run
Operate, measure, improve
Going live is the beginning.
We deploy with monitoring and a rollback plan, support what we shipped, and keep improving it from real usage. Documentation and handover are part of the job, so your team is never locked in.
- Monitored releases with a rollback plan
- Support and maintenance with agreed response times
- Documentation and handover to your team
Engagement models
Choose how we work together
Every project is different, so we do not publish a price list. Pick the model that fits your situation and we will send a clear, itemised quote.
Start here
Discovery sprint
Know exactly what to build, and what it will take.
One to three weeks- Workshops and system review
- Target architecture
- Prioritised backlog
- Budget and timeline estimate
- Written report you keep
Reply within two business days
Fixed-scope project
A defined result, for an agreed budget and date.
Defined scope and deadline- Specification agreed up front
- Milestone-based delivery
- Demo at each milestone
- Acceptance testing
- Warranty period after delivery
Reply within two business days
For evolving products
Dedicated team
A senior team that works as an extension of yours.
Monthly, scales up or down- Cross-functional team
- Your priorities, re-planned each sprint
- Demo every two weeks
- Direct access to engineers
- Flexible team size
Reply within two business days
Managed services
We run, monitor and improve what is in production.
Monthly, with service levels- Monitoring and alerting
- Security and dependency updates
- Incident response
- Monthly report
- Small evolutions included
Reply within two business days
Compare
Four models, side by side
The same people and the same standards in each one. What changes is how scope, budget and time are fixed.
| What changes | Discovery sprint | Fixed-scope project | Dedicated team | Managed services |
|---|---|---|---|---|
| Best for | Deciding what to build | A well-defined deliverable | A product that keeps evolving | Software already in production |
| Scope | Open: that is the point | Fixed in a specification | Flexible, re-prioritised each sprint | A defined perimeter of systems |
| Budget | Fixed price | Fixed price, paid by milestone | Monthly, by team size | Monthly fee |
| Team | Architect and lead engineer | Sized for the project | Cross-functional, sized with you | Shared operations team |
| Typical duration | One to three weeks | A few weeks to a few months | Ongoing, reviewed each quarter | Ongoing |
| Handling change | Not applicable | Through an agreed change request | Built in: you re-order the backlog | Small evolutions included, larger ones quoted |
| Reporting | Final written report | A demo at each milestone | A demo every two weeks, shared board | Monthly report |
| Who owns the code | You do | You do | You do | You do |
Scroll sideways to see every model.
Billing
Simple, predictable billing
You know what you will pay, when, and for what, before any work starts.
How each model is invoiced
The rhythm follows the way the work is delivered.
- Discovery sprint
- One invoice, issued when the report is delivered.
- Fixed scope
- Invoiced by milestone: each one is paid once you have accepted it.
- Dedicated team
- Invoiced monthly, for the team size agreed for that month.
- Managed services
- A monthly fee for the agreed perimeter and service levels.
What every quote includes
The same rules, whichever model you choose.
- Itemised
- Every quote lists what is included, line by line, and what is not.
- No lock-in
- No long commitment: the notice period is stated in the contract.
- Changes
- Anything outside the agreed scope is quoted before work starts, never after.
- Yours to keep
- Code, documentation and accounts are yours, and are handed over if we stop.
Questions
What clients ask us first
You do. Everything we write for you is assigned to you under the contract, and it lives in repositories you control. We keep no licence that would stop you from changing it or giving it to someone else.
Yes, and it is often the best set-up. We join your tools, your rituals and your code review, and take either a clearly bounded part of the product or a share of the common backlog. The aim is that your team is stronger when we leave.
It depends on the people the work needs and on what they are finishing. We tell you a realistic start date in the first call, before you commit to anything. A discovery sprint can usually begin sooner than a full build.
We break the work into pieces small enough to reason about, estimate each one as a range, and state our assumptions next to it. When too much is unknown, we say so and suggest a discovery sprint first instead of guessing a number.
Mainstream, well-supported technologies that your own team, or another supplier, could maintain after us. We choose them with you, according to your existing systems and skills. The technology page lists the tools we use most.
We work with the minimum data needed, in environments you approve, with access limited to the people on the project. For AI work, we agree beforehand which models and providers may see which data, and your data is not used to train a model without your written consent.
You receive the code, the documentation and a handover session. A fixed-scope project includes a warranty period during which we correct defects. After that you can run it yourselves, or ask us to run it under managed services.
Yes. We can sign yours, or send ours, before the first detailed conversation. Nothing you tell us is reused outside your project.
Next step
Not sure which model fits?
Tell us where you are. We will suggest the simplest way to start.
- A reply within two business daysFrom someone who can answer technical questions.
- An itemised quoteWhat is included, what is not, and the assumptions behind it.
- Confidentiality agreement on requestSigned before you share any detail.
Services · IT consulting
A technology plan you can act on
We look at your systems the way an engineer would, and explain what we find the way a business owner needs to hear it: what is solid, what is at risk, what to do first and what it will cost.
What we do
Three ways we help you decide
Audit and assessment
We review your architecture, code, infrastructure and running costs, interview the people who work with them, then tell you plainly what is solid, what is fragile and what to fix first.
Roadmap and architecture
A prioritised plan with a target architecture, budget ranges and milestones your teams can actually follow, written so that it survives contact with day-to-day work.
Technical leadership on demand
Senior guidance for the decisions that are expensive to get wrong: build or buy, choosing vendors, hiring, security. For a few days a month or for the length of a project.
How an engagement runs
From first conversation to a plan
A consulting engagement is short and ends with something you can use without us.
Frame the question
We agree what you need to decide, by when, and what a useful answer looks like.
Look at the facts
Code, infrastructure, costs, incidents and interviews with the people who know the system.
Share the findings
A working session on what we found, before anything is written down as final.
Hand over the plan
A written report and roadmap, presented to your team and to your management.
What you get
Documents you will actually open again
- A written assessment in plain language, with the evidence behind each finding.
- A risk list ranked by impact and by cost to fix.
- A target architecture, drawn and explained.
- A roadmap with priorities, milestones and budget ranges.
- A build-or-buy recommendation where it applies.
- A presentation session for your team and your decision makers.
How to start
The engagement models that fit this service
The highlighted ones are where most clients begin.
Discovery sprint
The natural format: one to three weeks, a fixed price, a written report.
Fixed-scope project
For a full assessment with a defined perimeter and delivery date.
Dedicated team
Technical leadership a few days a month, alongside your team.
Managed services
Not the usual route for consulting.
Start with a clear picture
Tell us what you need to decide. We will say whether a discovery sprint is enough.
Services · Software development
Software built to last
We design and build web applications, mobile apps and the services behind them. You see working software every two weeks, and you receive code your own team can read, test and extend.
What we do
What we build
Web and mobile applications
From customer portals to internal tools and mobile apps, designed with your users, tested with them, and delivered in short, visible iterations.
APIs, back ends and integrations
Reliable services that connect your product to your ERP, CRM, payment and partner systems, with clear contracts and error handling you can trust.
Modernising legacy software
We replace ageing systems step by step, behind the scenes, without stopping the business that depends on them and without a risky big-bang switch.
How an engagement runs
How a build runs
Small steps, each one finished and shown, so the plan can change without waste.
Shape
User journeys, a clickable prototype and a first backlog, agreed before any code.
Build
Two-week sprints, with tests and code review on every change.
Show
A demo on a real environment at the end of each sprint. You decide what comes next.
Ship
Release to your users, with monitoring, documentation and a handover.
What you get
More than a working screen
- Source code in your own repository, from the first day.
- Automated tests that run on every change.
- A staging environment where you can try each new version.
- Technical documentation and a guide to run the project.
- A demo every two weeks and a shared board.
- A handover session with your team at the end.
How to start
The engagement models that fit this service
The highlighted ones are where most clients begin.
Discovery sprint
To shape the product and estimate it before committing to a build.
Fixed-scope project
When the result is well defined: a specification, a budget, a date.
Dedicated team
For a product that keeps evolving after its first release.
Managed services
To keep what we built maintained and up to date.
Have something to build?
Describe it in a few lines. We will tell you how we would approach it.
Services · DevOps and cloud
Releases that are boring, in the best way
We automate the path from a change in the code to a version running in production, describe your infrastructure in code, and set up the monitoring that tells you about a problem before your customers do.
What we do
What we put in place
Automated delivery pipelines
Every change is built, tested and deployed the same way, so a release becomes a routine event instead of a risky one. Rolling back is one action, not an evening.
Cloud infrastructure as code
Environments described in code: reproducible, reviewed like any other change, and sized to what you really use, with costs you can read and explain.
Monitoring and reliability
Dashboards, alerts and clear runbooks, so problems are seen and handled before your customers notice them, and so the right person is woken up for the right reason.
How an engagement runs
How we get you there
We improve what exists first. Nothing is replaced unless it earns it.
Map
How a change travels to production today, where it waits and where it breaks.
Automate
Build, tests and deployment in a pipeline, starting with the slowest manual step.
Codify
Environments, networks and permissions described in code and reviewed.
Watch
Monitoring, alerts and runbooks, then a handover to the people on call.
What you get
Infrastructure you can understand
- A pipeline that builds, tests and deploys every change.
- Infrastructure code in your repository, with documentation.
- Separate environments for development, staging and production.
- Dashboards and alerts on what matters to your users.
- Runbooks for the most likely incidents, and a rollback procedure.
- A cost overview, with the main savings available.
How to start
The engagement models that fit this service
The highlighted ones are where most clients begin.
Discovery sprint
A review of your delivery process and cloud set-up, with a costed plan.
Fixed-scope project
A pipeline or a migration with a defined result and date.
Dedicated team
Platform engineers working with your developers.
Managed services
We run, monitor and update the platform with agreed service levels.
Make your next release uneventful
Tell us how you deploy today. We will show you the first thing we would automate.
Services · AI services
Useful AI, under your control
We put AI to work on specific, measurable jobs in your business: answering questions from your own documents, taking the repetitive part out of document-heavy work. A person stays in charge of what matters.
What we do
Where AI earns its place
Assistants on your own knowledge
Chat and search over your documents and data, with answers that cite their sources and respect your access rights, so people can check what they are told.
Automating document-heavy work
Extraction, classification and drafting for the repetitive tasks that slow your teams down, with a person approving what matters before it leaves the building.
From prototype to production
We measure quality before launch, monitor it afterwards, and keep cost and data privacy under control. A demo that impresses is not the same as a tool people rely on.
How an engagement runs
How an AI project runs
We prove the value on a small, real case before anyone invests in the rest.
Choose the job
One task, with a clear owner and a way to measure whether it got better.
Prototype on real data
A working version on your documents, in an environment you approve.
Measure
A test set built with your experts: how often it is right, and how it fails.
Put into service
Integration, access rights, monitoring and a person in the loop where needed.
What you get
An AI tool you can stand behind
- A written evaluation: accuracy on your own test cases, and known limits.
- Answers that cite the documents they come from.
- Access rights that follow the ones you already have.
- A review step for anything sent to a customer or recorded as official.
- Cost and usage monitoring from the first day.
- A written description of which data goes where.
How to start
The engagement models that fit this service
The highlighted ones are where most clients begin.
Discovery sprint
To pick the right use case and test it on your real data.
Fixed-scope project
A defined assistant or automation, with agreed quality targets.
Dedicated team
When AI becomes a lasting part of your product.
Managed services
Monitoring quality and cost once it is in service.
Have a task in mind?
Tell us which one. We will say honestly whether AI is the right tool for it.
Who we work with · Startups
From idea to first paying users
You need a real product in front of real users, soon, without building something you will have to throw away in a year. We help you ship a first version that is small, sound and yours.
Typical needs
A first versionSpeedSound technical foundationsCost controlA technical partner
Before and after
Where early products usually go wrong
The usual situation
- Too much, too earlyMonths spent on features nobody has asked for yet, and a launch that keeps moving.
- A prototype pushed into productionIt worked for the demo. It does not survive the first hundred users.
- Nobody owns the technical choicesDecisions are made by whoever is available, and nobody can explain them later.
With Aggregax
- The smallest version that proves the ideaWe cut the scope with you until what is left can ship in weeks, not quarters.
- Foundations sized for the next stageSimple architecture, automated deployment, tests on what matters. Nothing more.
- Choices you can explain to investorsEach technical decision is written down with its reason and its cost.
How we fit in
A typical path for a startup
You can stop after any step and keep what has been produced.
Discovery sprintScope the first version and estimate it honestly.Software developmentBuild and release it in short iterations.DevOps and cloudAutomate releases and keep the cloud bill small.
HandoverHelp you hire, then pass the product to your own team.
Results
What we usually deliver
A first version in production
Used by real customers, with the analytics to learn from them.
A codebase your first hires can take over
Readable, tested and documented, in your own repository.
A running cost that matches your stage
Infrastructure that starts small and grows only when usage does.
Building your first version?
Tell us about the idea and the deadline. We will say what can realistically ship.
Who we work with · Scale-ups
Grow without the platform holding you back
The product works and customers are arriving. Now releases are slowing down, incidents are more frequent and hiring cannot keep up. We help you scale the platform and the way you deliver.
Typical needs
Scaling the architectureDelivery automationExtending the teamReliabilityCloud costs
Before and after
The growing pains we see most
The usual situation
- Releases get slower as the team growsMore people, more coordination, and every deployment needs a meeting.
- The platform creaks under loadPerformance problems appear at the worst moment, and fixes are rushed.
- Hiring is the bottleneckThe roadmap waits for people you have not found yet.
With Aggregax
- A pipeline that removes the waitingAutomated tests and deployments, so teams release independently and often.
- Architecture changed where it countsWe measure first, then change the few parts that actually limit you.
- Senior capacity straight awayA team that is productive in days and works to your standards.
How we fit in
A typical path for a scale-up
We start where the pain is greatest, and prove the result before going further.
Results
What we usually deliver
A faster, calmer release process
From a change in the code to production in a routine, reversible step.
A platform with known limits
Load tested, monitored, and with a plan for the next order of magnitude.
A team that grew without slowing down
Shared practices, documentation and onboarding that your hires benefit from too.
Is the platform slowing you down?
Tell us where it hurts. We will suggest where to look first.
Who we work with · Enterprises
Modernise without stopping the business
Your systems run the company, and some of them are older than the people who maintain them. We help you replace what must be replaced, connect what must stay, and do it without a risky big-bang switch.
Typical needs
Legacy modernisationIntegrationGovernanceSecurityKnowledge transfer
Before and after
What makes modernisation hard
The usual situation
- A system nobody dares to touchIt works, it is critical, and the people who built it have moved on.
- Projects that try to replace everythingYears of work before the first benefit, and a switch-over everyone fears.
- Suppliers who keep the keysDocumentation is thin, and changing provider looks impossible.
With Aggregax
- The existing system, understood and documentedWe map what it does and what depends on it before changing anything.
- Replacement in steps, each one in serviceNew parts run beside the old ones, and take over one function at a time.
- Everything handed to youCode, documentation, access and know-how are transferred as part of the work.
How we fit in
A typical path for an enterprise
Each step fits your governance: steering committees, security reviews, change management.
Results
What we usually deliver
A staged modernisation plan
With the risks, the dependencies and the cost of each stage.
New components running beside the old
Integrated with your directory, your ERP and your security rules.
Documentation and training
So that your teams, or another supplier, can take over at any point.
Planning a modernisation?
Tell us which system worries you most. We will explain how we would approach it.
Who we work with · Product teams
Extra senior hands, exactly where you need them
You already have a team and a way of working. What you lack is time, or a skill you do not need full time. We join you on development, DevOps or AI, and fit into the way you already work.
Typical needs
Reinforcing a teamA missing skillA deadlineCode reviewMentoring
Before and after
What reinforcing a team often looks like
The usual situation
- Weeks before a newcomer is usefulOnboarding takes more of your seniors’ time than it gives back.
- A parallel team with its own habitsDifferent tools, different standards, and a merge nobody enjoys.
- Knowledge that leaves with the contractorThe work is done, but nobody in-house can explain it.
With Aggregax
- Senior engineers who are productive in daysThey read the code, ask the right questions and take real tickets quickly.
- Your tools, your rituals, your code reviewWe work in your repository and follow your definition of done.
- Knowledge that stays with youPairing, documentation and reviews are part of the job, not an extra.
How we fit in
Where we usually plug in
One specialist for a few weeks, or a small squad for a quarter.
Results
What we usually deliver
Features shipped inside your process
Reviewed and merged like those of any other member of the team.
A skill your team keeps
What we know about the subject is shared as we go.
A clean exit
No part of the product depends on us when the engagement ends.
Need more capacity this quarter?
Tell us about your team and your stack. We will say who could join, and when.
Why Aggregax · Overview
One team that advises, builds, runs and improves
Aggregax is an IT services company. We help organisations decide what to build, build it, put it into production and keep it healthy, with the same people from the first conversation to the day it runs.
- Services
- IT consulting, software development, DevOps and cloud, AI services.
- Works with
- Startups, scale-ups, enterprises and product teams.
- Languages
- English and French.
What we do
Four services, one continuous chain
Each service stands on its own. Together they cover the whole life of a piece of software, with no handover between suppliers.
Who it is for
Organisations at four different moments
Scale-ups
A platform and a delivery process that keep up with growth.
Enterprises
Legacy systems modernised in steps, without stopping the business.
Product teams
Senior reinforcement that fits into the way you already work.
What stays the same
Whatever the service, you can count on this
- The people you meet first are the people who do the work.
- Working software shown at the end of every iteration.
- A shared board, so you always know where things stand.
- Code, documentation and accounts that belong to you.
- A written quote before any work starts.
- A handover planned from the beginning.
See if we are the right fit
Thirty minutes is enough to know. Tell us where you are and what you need.
Why Aggregax
What working with us actually looks like
Most disappointments with a technology supplier come from the same few causes: you never talk to the people doing the work, you find out late, and you cannot leave. We organised ourselves to avoid all three.
- Who does the work
- Senior engineers, the ones you met.
- How you follow it
- A demo every two weeks.
- Who owns it
- You do. All of it.
Side by side
The usual agency experience, and ours
The usual experience
- Sold by seniors, built by juniorsThe experts from the first meeting disappear once the contract is signed.
- Progress reported, not shownWeekly status reports say everything is on track, until the week it is not.
- Dependence by designThe code is hard to take over, and the documentation arrives at the end, if at all.
- Yes to everythingEvery request is accepted, and the budget quietly follows.
With Aggregax
- The same people, start to finishYou speak directly to the engineers who design and write your software.
- Working software every two weeksYou try it yourself on a real environment and decide what comes next.
- Built to be handed overYour repository, your accounts, documentation written as we go.
- A clear no, with the reasonWhen something is not worth building, we say so and suggest what is.
Principles
Four things we hold ourselves to
Senior people do the work
Small teams of experienced engineers. No layer between you and them.
You see progress every two weeks
A demo of working software, not a slide about it.
You own everything
Code, infrastructure, documentation and data are yours from the first day.
We say no when it is the right answer
To a feature, to a technology, sometimes to a project.
In practice
What this means for you
Fewer surprises
Problems appear in a demo after two weeks, not in a delivery after six months.
Decisions you can defend
Each important choice is written down with its reason, its cost and its alternatives.
Freedom to leave
Everything needed to continue without us exists and is in your hands.
Judge for yourself
Talk to the people who would do the work, before you decide anything.
Why Aggregax · Book a call
Thirty minutes, with the people who would do the work
No sales script. Tell us what you want to build, fix or speed up, and we will tell you honestly how we would go about it.
What happens in the call
Three things, in half an hour
You describe your situation
Where you are, what you want to achieve, and what is in the way.
We ask the questions an engineer would
About your users, your systems, your constraints and your deadline.
We suggest a way to start
The simplest first step, and the engagement model that fits. Or we tell you we are not the right choice.
Prefer e-mail? Write to us at contact@aggregax.example.
About
A technology partner you can hold to account
Aggregax designs, builds and runs software for companies that want to move faster without losing control. We are engineers first: we would rather show you something working than describe it.
- Services
- IT consulting, software development, DevOps and cloud, AI services.
- Languages
- English and French.
- Based in
- To be confirmed
- Founded
- To be confirmed
Good software is mostly good decisions, made early and made together.
What we do
Three things, done by the same people
We advise
We look at your systems and your plans, and tell you plainly what we would do in your place, and why.
We build
Web and mobile applications, the services behind them, and the AI features that make them more useful.
We run
We automate delivery, watch over what is in production and keep improving it from real usage.
Values
What guides our work
Clarity
Plain words, written decisions, honest estimates. You should never have to guess where things stand.
Ownership
We answer for what we deliver. And what we deliver belongs to you.
Craft
Tested, reviewed, documented. Code written to be read by the next person.
Long-term thinking
We choose what will still make sense in three years over what looks impressive today.
Future solutions, built today
Meet the people behind Aggregax and tell us what you are working on.
Resources · Technology
Tools we choose because they last
We work with mainstream, well-supported technologies that your own team, or another supplier, could maintain after us. These are tools we use, not partnerships or certifications.
- How we choose
- Maturity, community, and the skills you already have.
- What we avoid
- Technology chosen because it is new.
By area
What we work with
Front end
Web interfaces and design systems.
List to be added
Back end
APIs, services and business logic.
List to be added
Mobile
Applications for phones and tablets.
List to be added
Data
Databases, pipelines and reporting.
List to be added
Cloud and DevOps
Hosting, delivery pipelines and monitoring.
List to be added
AI
Language models, retrieval and evaluation.
List to be added
Placeholder content. The technologies in each area will be listed here once Aggregax has confirmed them.
Principles
How we pick a technology for you
Start from what you have
Your existing systems and the skills of your team weigh more than our preferences.
Prefer the well-trodden path
Widely used tools, with long-term support and people you can hire.
Write the reason down
Each choice is recorded with what it costs and what it rules out.
Working with a specific stack?
Tell us which one. We will say plainly whether we know it well.
Company · Selected work
Case studies, told plainly
Each one follows the same structure: the context, what we did, and the result. We publish a case study only with the client’s agreement.
Case studies
Three projects, to be added
Case study to be added
- Context
- To be added: the client’s situation and what was at stake.
- What we did
- To be added: the work carried out and the choices made.
- Result
- To be added: what changed, with figures the client has approved.
Case study to be added
- Context
- To be added: the client’s situation and what was at stake.
- What we did
- To be added: the work carried out and the choices made.
- Result
- To be added: what changed, with figures the client has approved.
Case study to be added
- Context
- To be added: the client’s situation and what was at stake.
- What we did
- To be added: the work carried out and the choices made.
- Result
- To be added: what changed, with figures the client has approved.
Placeholder content. No client or result is shown until a real case study has been approved for publication.
Want to know if we have done something similar?
Ask us in a call. We will tell you what we can share.
Resources · Insights
Notes on building and running software
Practical writing from the people who do the work: what we tried, what held up, and what we would do differently.
- Status
- No article published yet.
- Newsletter
- Leave your address in the footer to hear about the first ones.
Engineering
Article to be added
To be added: title, summary and link, once the article is written.
Delivery
Article to be added
To be added: title, summary and link, once the article is written.
AI
Article to be added
To be added: title, summary and link, once the article is written.
Placeholder content. Articles will appear here as they are published.
Hear about new articles
Occasional notes, no more. You can unsubscribe at any time.
Company · Careers
Do careful work, with people who care
We are a small team of engineers who like understanding a problem properly, building the simplest thing that solves it, and staying around to see it used.
- Open positions
- None listed at the moment.
- Open applications
- Always read, always answered.
- Languages
- English and French.
How we work
What a week looks like
Small teams, real responsibility
You talk to the client, take part in the decisions and see your work in production.
Time to do things properly
Tests, reviews and documentation are part of the estimate, not what is cut first.
Learning as part of the job
Pairing, code review and a new subject on most projects.
Who we look for
Three things matter more than a list of tools
You explain things clearly
To a colleague, and to a client who is not technical.
You finish what you start
Including the unglamorous last ten per cent.
You say when you do not know
And then you go and find out.
To send an open application, write to careers@aggregax.example and tell us what you would like to work on.
Resources · Security & quality
Careful by habit, not by exception
Quality and security are not a phase at the end of a project. They are the way each change is written, reviewed, tested and released, every day.
- Every change
- Reviewed by a second engineer.
- Every release
- Tested automatically, reversible.
- Every access
- Named, limited, removed at the end.
Quality
How a change reaches production
Written with tests
New behaviour comes with the tests that prove it.
Reviewed
A second engineer reads every change before it is merged.
Checked automatically
The pipeline builds, tests and scans it.
Released reversibly
Deployed with monitoring and a way back.
Security
How we handle access and data
Access
Individual accounts, the least privilege that does the job, and removal when the engagement ends.
Secrets
Passwords and keys live in a secrets manager, never in the code or in a message.
Client data
We work on the minimum data needed, in environments you have approved.
AI data
We agree in writing which models and providers may process which data, before any is sent.
In your contract
What we commit to in writing
The exact terms are set in each contract. These are the subjects we always cover.
- Confidentiality, signed before you share any detail.
- Ownership of the code and of everything we produce for you.
- Where your data is processed, and by whom.
- What happens to data and access at the end of the work.
- How a security incident is reported to you.
- Dependency and security updates, under managed services.
This page describes how we work. It is not a certification, and it does not replace the terms of your contract.
Have a security questionnaire?
Send it to us. We answer them precisely, and say so when a point does not apply.
Legal
Legal notice, who is behind this site
The information a visitor is entitled to know about the publisher and the host of this website.
Placeholder content. The company details below are still to be supplied by Aggregax, and the wording must be checked against the law of the country where the company is registered.
Publisher
This website is published by the company identified below.
- Company name
- To be confirmed
- Legal form and capital
- To be confirmed
- Registration
- To be confirmed
- VAT number
- To be confirmed
- Registered office
- To be confirmed
Publication director
- Name
- To be confirmed
Contact
- To be confirmed
- Phone
- To be confirmed
Hosting
This website is hosted by the provider identified below.
- Host
- To be confirmed
Intellectual property
The texts, illustrations, logo and layout of this website belong to Aggregax, unless stated otherwise. They may not be reproduced or reused without prior written permission.
The names of third-party products and technologies mentioned on this site belong to their respective owners. Mentioning them does not imply a partnership or an endorsement.
Liability
The information on this website describes our services in general terms. It is not a contractual offer: only a signed quote or contract commits Aggregax.
We take care to keep this site accurate and available, but we cannot guarantee that it is free of errors or interruptions.
External links
This site may link to other websites. We have no control over their content and are not responsible for it.
Legal
Privacy policy, in plain language
What this website collects, why, and what you can ask us to do about it.
Placeholder content. This is a draft that describes how the site works today. Retention periods, recipients and the legal basis must be confirmed by Aggregax before publication.
Who is responsible
The company that publishes this website decides how the data described here is used.
- Data controller
- To be confirmed
- Privacy contact
- To be confirmed
What this site does not do
- It does not set cookies.
- It does not use analytics or advertising trackers.
- It does not ask you to create an account.
- It loads its fonts from its own server, not from a third party.
When you write to us
If you use the contact form or the call request form, we receive what you type: your name, your work e-mail address, your company if you give it, and your message.
We use this only to answer you and to prepare the conversation you asked for.
Newsletter
If you ask to receive the newsletter, we keep your e-mail address to send it to you. You can unsubscribe at any time by writing to us.
How long we keep it
We keep your message for as long as the exchange lasts, and then for a limited period that will be stated here.
- Retention period
- To be confirmed
Who can see it
Only the people at Aggregax who need it to answer you, and the service providers that host our e-mail and this website. We do not sell or rent personal data.
- Service providers
- To be confirmed
Your rights
You can ask us to show you the data we hold about you, to correct it, to delete it, or to stop using it. Write to the privacy contact above. If you are not satisfied with our answer, you can contact the data protection authority of your country.
Changes to this policy
If the way this site handles data changes, this page will be updated before the change takes effect.
Contact us
Tell us what you want to build, fix or speed up. A senior engineer reads every message and replies with concrete next steps.
Message sent
Thank you. We have received your message and will reply within two business days.
Your e-mail app has opened with your message
Press send there to reach us. If nothing opened, write to us directly at contact@aggregax.example.