Stop being your clients' hosting team.
You sell Odoo implementation. Odoo hosting is the part you never quoted for, never wanted, and still get called about at 2am. Hand it to the people who ran Odoo's technical consultancy: on our cloud, on your client's own server, or entirely inside their network, under a formal SLA and an ISO 27001 certification you can cite in your own proposals.
And you keep 20% of every hosting contract, for the life of the client.
No servers to manage · No 2am calls · Community & Enterprise · ISO 27001 · Formal SLA · 20% recurring, uncapped
Odoo hosting is the part of the job nobody is paying you for.
You have had one of these weeks. A log file quietly ate the disk on a client's server, and the first anyone knew was when Odoo stopped responding. A staging environment built by copying the production VM, so real customer records and live email addresses sat in a test database nobody had locked down. An update that went straight to production because there was no pipeline to put it anywhere else, and took the whole system offline on a Tuesday morning.
None of that is a competence problem. Your team can run Linux, manage a database and ship code. Odoo hosting is a narrow specialisation (workers, websocket, longpolling, cron threads, log rotation, Odoo-specific backups, sanitised staging) and there is no good reason for an implementation team to have acquired it.
It is also not what your client is paying you for. Every hour on infrastructure is an hour not billed on implementation, it always arrives unscheduled, and it lands hardest in the week you are busiest.
Hand it over and it stops being yours. Not delegated, not shared between you and a VPS provider who has never heard of Odoo. Gone.
The work you never quoted for
Server provisioning, SSL renewals, backup verification, version upgrades, the odd 3am restart. None of it appeared on the statement of work, all of it lands on your team, and none of it is invoiceable: a standing deduction from the margin on every project you have delivered.
The 2am problem that isn't your product
When a client's Odoo goes down, they call you, not their VPS provider. You inherit an availability obligation you never signed up for, without the monitoring, the failover or the rota to meet it. One bad night costs more goodwill than the hosting ever earned.
The cost that scales with every client you win
Hosting looks like found revenue until you price the hours. Patching, monitoring, restores, incident response and the context-switching around them are real cost, and they grow with every client you add. The tenth client does not get cheaper to host. It gets harder.
Three ways to host a client. One platform.
Handing hosting over only helps if it covers every client, not just the straightforward ones. Most platforms give an agency one model and expect every client to fit it, which works until the client with a data-residency clause, or an existing cloud contract, or a security policy that says nothing leaves the building, walks through your door. Then you lose the deal on infrastructure rather than on your work.
Skysize covers the whole range from one partner account. The operations layer never changes: Odoo configured and run the way the people who led Odoo's technical consultancy run it. The only thing that changes is who holds the infrastructure.
Managed cloud: the client wants none of it
The client wants Odoo to work and has no opinion about servers. We host it, we run it, and neither you nor they touch infrastructure at any point. Deployments, staging, backups, monitoring and upgrades are ours. You do the implementation, keep the client relationship, and carry zero operational load, which is the model most SMB clients actually want when somebody asks them plainly. See managed Odoo hosting for your clients.
Their server, their cloud, their region, managed by us
The client has an existing cloud contract, a data-residency requirement, or a policy that says the machine has to be theirs. They provision the server at any provider in any region; one command installs a lightweight agent; Skysize orchestrates deployments, staging and Git-based CI/CD on their machine from there. They own the box and the data. We run Odoo on it. This is the model DevOps-capable agencies tend to want for themselves as well: you can host clients on their own server without becoming the Odoo hosting team.
On-premise: nothing leaves their network
The bank, the hospital, the government department, the defence supplier. Both the agent and the controller run inside the client's own network, with no inbound connections required and air-gapped operation supported via an internal Docker registry. Automated deployment, daily log rotation, Odoo-specific backups and automatically sanitised staging, inside their walls, under their control. When a client's security policy rules out the cloud entirely, this is what keeps the deal alive: on-premise Odoo for regulated clients, available to partners white-labelled.
Whichever model the client needs, nothing changes on your side. One platform, one dashboard, one partner agreement, and the same 20% commission on all three.
Or run the platform yourself: your own Odoo cloud, under your own brand
There is a version of this partnership where you do not send clients to a hosting provider at all. You become one.
Skysize On-Premise is the platform we built to run Odoo correctly on infrastructure we do not own. It can be licensed to you, installed on your own servers, and run as a multi-tenant hosting platform for your whole client base, under your own brand. Your clients sign with you. You set your own pricing. You hold the billing relationship outright. We are the software underneath, and we stay out of sight.
If you have ever seriously considered building this yourself, you have already costed it. A control plane. A deployment pipeline. Backup and restore that understands Odoo databases and filestores rather than whole virtual machines. Staging automation with sanitisation a compliance officer would actually accept. Monitoring, log rotation, upgrade tooling, a dashboard your clients can be given access to. And then the part that never makes it into the estimate: maintaining all of it indefinitely, while Odoo ships two major versions a year and each one moves something underneath you. That is a permanent product team, not a project, and it is not the work your clients are paying you for.
The platform already exists. It is in production today, including inside regulated networks where nothing is allowed to leave the building. You can be running it under your own brand next quarter rather than in two years.
Multi-tenant, on infrastructure you control
One installation, many client deployments, managed from a single interface. Automated deployment with the Odoo-specific configuration already correct, Git-based CI/CD, sanitised staging, Odoo-specific backups, daily log rotation and multi-server management: the same platform capabilities described on the on-premise Odoo deployment platform page, operated by your team instead of ours.
Your brand, your pricing, your billing relationship
The platform carries your name in front of your clients. You decide what hosting costs on your side, what is bundled with an implementation, and what is billed separately. Clients contract with you and pay you. Nothing in that relationship routes through us, and nothing about it needs to mention us.
A licence, not a commission
This tier inverts the commercial model. Instead of us billing the client and paying you 20%, you license the platform for an annual fee, run it yourself, and keep the hosting revenue. It is quote-based and scoped to your deployment, so the first conversation is a technical and commercial one rather than a sign-up. It is also a different decision from the commission programme: most partners start on commission and move here only once the client base makes it worth owning the platform.
Where this stops being theoretical
It fits agencies with an established base of Odoo clients, a team that can operate Linux servers and PostgreSQL, and a reason to own the hosting relationship rather than introduce it: data residency commitments, a national market that expects a local provider, or simply enough clients that hosting has become a line of business in its own right. If you are not there yet, the commission programme is the better starting point and we will say so on the call.
Considering running the platform yourself? Book a licensing conversation: technical scope first, quote after.
Discuss a platform licence →20% recurring, uncapped, for the life of the client
Relief from the operational load is the reason to move. This is what makes it worth doing for every client after the first.
Every client you host on Skysize earns you 20% of their hosting contract, paid monthly, for as long as that client stays. Not a one-off referral fee. Not a first-year bonus that quietly stops. A recurring line on your revenue that grows with every client you deploy and keeps paying while you are working on something else entirely, with nothing to qualify for and nothing to maintain. It is 20%, from the first client, indefinitely.
No caps, no minimums, no tiers
No ceiling on what you can earn and no floor to clear before you start. One client qualifies; so does fifty. No tiers to climb, no annual KPIs, no certification requirements, no revenue commitment and no minimum contract length on your side. The rate is the same for a two-person implementation shop and a forty-person agency, and it applies to Odoo Community contracts exactly as it does to Enterprise. The edition your client chooses does not change what you earn.
Paid for the life of the client, not the first year
If a client you introduced in year one is still with us in year five, you are still being paid on them in year five, whether or not you are still doing implementation work for them. The book you build is an asset, not a pipeline you have to keep refilling to stand still.
A transparent partner dashboard
Every client, every invoice, every commission line in one place, whenever you want to look. No statements to request, no spreadsheet reconciliation at quarter end, no surprises on either side.
See what your book could earn
Enter your own numbers. This is an illustration based on the figures you type in.
Illustrative, based on the figures you enter. Your commission is 20% of the Skysize hosting contract value. Pricing is regional; see pricing for your region.
ISO 27001 your client's procurement team can actually check
The moment your client is regulated (finance, healthcare, public sector, or anyone with a serious procurement process) someone sends you a security questionnaire and asks who hosts the system. That question either ends the conversation, or costs you a week of chasing a vendor for a document that turns out not to exist.
You can inherit ours instead.
Certificate number, auditor, scope: published
Our ISO 27001 certification is published with the certificate number, the certification body that issued it, and the scope statement of what it covers, on a page you can send to a procurement team without editing anything. A certification you cannot cite is not evidence. This one is: see our ISO 27001 certificate and scope.
A formal SLA in writing
A published service level agreement with a 99.5% uptime commitment and committed support response times. A real contract, not a marketing line. Your client's legal team can read it before they sign, and you can attach it to your proposal instead of writing availability promises of your own that you would then personally have to meet. Read our service level agreement.
Cite it in your own proposals
You have our explicit permission to reference our certification, our SLA and our infrastructure in your client proposals and tender responses. We maintain a partner one-pager covering certification, scope, data handling and the SLA, written to be dropped straight into a bid pack. Ask for it on your partner call and it is yours.
White-label: we run it, your brand is on it
Everything in the three models (our cloud, your client's server, their network) can carry your brand instead of ours. We operate the platform; the client sees your agency. Infrastructure should be invisible, and the relationship you built should stay yours.
Your brand in front of the client
Your domain, your logo, your colours on the interface your client logs into. As far as the client is concerned, the hosting is part of what your agency delivers, because from their side, it is. Behind it, we are the ones running, monitoring and supporting the platform. You get the brand without the rota.
We never sell consultancy. Ever.
Skysize does not sell implementation, customisation or consultancy services. Not now, not as a future product line. We have a written non-solicitation commitment covering your clients, and there is no scenario in which we compete with you for the work you introduced us to. Our business is hosting. Yours is everything around it. That separation is the whole basis of the partnership.
White-label on-premise too
Your brand extends to on-premise deployments. If your client cannot use the cloud at all, you can put a full on-premise Odoo deployment platform in front of them under your own name: a product you can take into a tender for a bank or a government department, branded as yours throughout. Whether you or your client's IT team operates it day to day is a separate decision, and one we will work through with you.
How the partnership works
Four steps, no application process to survive.
Book a call
Thirty minutes with Benjamin, who ran Odoo's technical consultancy before building this. You describe your client base and how you host today; we tell you honestly which of the three models fits and whether the partnership is worth your time. No deck, no qualification interrogation.
We set up your partner account
We create your partner account, walk you through the dashboard, and go through the partner agreement together: commission terms, non-solicitation, white-label options, and what each side is responsible for. You will have read it before you sign anything.
Deploy your first client
Pick the model that suits that client (our cloud, their server, or their network) and deploy. We help with the first one directly, including migrating an existing Odoo instance if the client is already running somewhere else. After that, deployments are self-service.
Commission starts, and keeps going
Commission begins with that client's first paid invoice and is paid monthly for as long as they stay. Every client, invoice and commission line is visible in your dashboard, and you can see pricing for your region at any time.
Built by the people who ran Odoo's technical consultancy
Skysize was founded by Benjamin Akboka Apengu, former Head of Technical Consultancy at Odoo Dubai, and his co-founder, also formerly of Odoo. Between them they deployed and supported Odoo in enterprise and government environments across Europe and the Middle East: the deployments where the security review is longer than the implementation and getting the hosting wrong is not a recoverable mistake.
That is the whole reason this platform exists. Everything it automates (worker and websocket configuration, daily log rotation, Odoo-specific backups rather than VM snapshots, sanitised staging, Git-based CI/CD) is something we watched go wrong repeatedly in the field, packaged so it cannot go wrong again.
Today more than 200 companies run Odoo on Skysize across all tiers, on Community and Enterprise, on our cloud, on their own servers and inside their own networks. When you have a question your team cannot answer, you are talking to the people who wrote the platform, not a support tier.
(all tiers)
infrastructure
Partner FAQ
01 How much commission do partners earn, and for how long?
02 Is there a minimum number of clients or a tier to qualify for?
03 When is commission paid, and how do I track it?
04 Can I host clients on their own servers instead of yours?
05 Do you support Odoo Community as well as Enterprise?
06 Can I resell Skysize under my own brand?
07 Will you sell consultancy or implementation services to my clients?
08 Can I offer on-premise Odoo to clients who can't use the cloud?
09 Can I license the platform and run it myself for my own clients?
10 How is running the platform myself different from the 20% commission programme?
11 Is this related to the official Odoo partner programme?
12 What happens to my clients' data if I leave the programme?
Bring us your next client's hosting.
Book a call and we will go through your client base, how you host today, which of the three models fits, and the commission terms. Honestly, including whether this is a fit at all. Every Skysize partner started with a conversation.
No servers to manage · Managed, your server, or on-premise · Community & Enterprise · White-label available · Platform licensing available · ISO 27001 · Formal SLA · 20% recurring, uncapped, no minimums