Hosting and AWS resale
We hold the AWS accounts, or we work in yours. In the first case you get a single invoice in euros, broken down per environment, and no dollar-denominated contract to manage internally.
AWS Hosting & Managed Services
We operate what we build
Hosting on AWS, on-call, monitoring, application and infrastructure maintenance, and continuous cost control. We bill infrastructure in euros, and we answer when it rings.
What maintenance and operations actually cover
Plenty of projects survive their launch and fail eighteen months later, when nobody left in the building knows why an alert fires. Managed services exist to prevent exactly that: somebody knows the system, watches it, patches it, and answers when it breaks.
In practice we take on hosting the solution on AWS, supervision, on-call, corrective and evolutionary maintenance, keeping the platform in operational condition, and cost control. We can also hold the commercial relationship with AWS and re-invoice the infrastructure to you in euros, on a bill you can actually read.
We prefer to operate what we built, because that is where we are worth the money. But we also take over existing platforms, after an assessment that says honestly what can be operated as it stands and what has to be fixed first.
What the contract covers
Six commitments, all of them written into the contract rather than implied.
Monitoring and alerting
Metrics, logs, traces, dashboards, and alerts that mean something. An alert that fires with no action attached to it is a defect, and we treat it as one.
On-call
A number that reaches one of us two, not a first-line support desk that will ask you to restart it. The hours and the terms are written into the contract rather than promised in a meeting.
Corrective and evolutionary maintenance
Bug fixes, version upgrades, dependency and security patching, small functional changes. An agreed monthly volume, prioritised with you.
Keeping it operable
Tested backups, recovery plans, security updates, secret rotation, periodic architecture reviews. The invisible work that stops the incident from happening.
Continuous FinOps
Monthly bill review, drift detection, right-sizing, Savings Plans. We flag savings even when they reduce the infrastructure we invoice, because the alternative is charging you for our own inattention.
How a contract starts
We will not put an on-call promise on a platform we cannot yet supervise.
Takeover assessment
We look at what exists: architecture, debt, backups, secrets, documentation. You get a clear statement of what is operable as it stands and what has to be fixed first.
Bringing it up to standard
The minimum work to make the platform observable and recoverable. Without this step, an on-call commitment is an empty promise.
Instrumentation
Monitoring, alerts, dashboards, and written operating procedures for the things that go wrong.
Operations
Steady state: supervision, on-call, maintenance, and a monthly review of costs and incidents with you.
In Lyon, and reachable anywhere
We are in Lyon, in your time zone, and you speak to the person who wrote the code or built the infrastructure. We travel to clients on site, in France or abroad, when a subject deserves a face-to-face discussion. For everyone else it is remote, which has never stopped anyone from picking up the phone when it matters.
Related case studies
All case studiesQuestions we get asked
Can you take over a platform you did not build?
Yes, after a takeover assessment. What we refuse is an on-call commitment on a system we cannot supervise or restore, because that would be selling insurance with no cover behind it.
How is it billed?
A monthly fee for operations, plus AWS infrastructure re-invoiced at actual cost if we hold the accounts. The maintenance volume is agreed up front. We do not bill per incident, because that would pay us to let things break.
What exactly does on-call cover?
The hours, the response times and the technical scope are written into the contract. We would rather commit to something modest and honour it than promise 24/7 cover that two people cannot genuinely guarantee alone.
Do we own the infrastructure?
Yes. If we hold the AWS accounts they are transferable, and the exit is part of the contract: you leave with your accounts, your data and your infrastructure as code.
Do you have to have built it?
No, but it is the most effective arrangement. When we built the platform, there is no dark corner to discover at three in the morning.
Do you provide reporting?
Yes: a short written monthly review covering incidents and their root cause, the corrective actions taken, how costs are trending, and what we think deserves attention next. It is written to be read by someone making decisions, not to be a dump of metrics nobody opens. You also get real-time access to dashboards and alerts so nothing comes as a surprise.
The other two things we do
AWS Consulting
We audit existing AWS estates, design architectures that hold, and bring costs back under control. Short, scoped engagements run by the two of us, based in Lyon.
Product Development
We design and build platforms on AWS, from the first framing session to the run phase. Two people, code we stand behind, and an architecture built to be handed over.
Talk to us directly
Write to us directly. No salesperson, no qualification call. One of us two replies, within 24 hours.
contact@onescale.io
We reply within 24 hours, and it is one of us who replies.
Based in Lyon, working with clients in France, across Europe and internationally.