Eza Cloud for agencies
Host client apps without chasing hosting money
Create one Eza organisation per client. They receive their own billing contact and pay Eza directly by M-Pesa. You keep access while you build and support their Laravel, WordPress or Node app.
- One organisation per client
- M-Pesa billing
- Unlimited team members
- 10% referral credit
juma-bakery
WordPress multisite · Billing contact: Client
Current organisationHobbyAdminkilele-logistics
Laravel API · Billing contact: Client
StarterAdminmtaa-clinics
Next.js web app · Billing contact: Client
ProAdmin
The agency problem
Hosting should not sit in your personal M-Pesa
A client pays you for a website. You pay for the server. The renewal date arrives before the client sends the money.
That setup makes handovers difficult. It also makes billing unclear when one server runs several client sites.
Eza gives every client their own organisation, plan, invoice and billing contact.
The client pays Eza directly by M-Pesa. Your agency keeps the access needed to deploy, maintain and support the app.
How client organisations work
One client, one Eza organisation
Create a separate Eza organisation for each client.
Your agency can belong to many client organisations.
Your client can add their own Owner, Admin, Member or Viewer accounts.
Read team rolesEach organisation has:
- Its own hosting plan
- Its own billing contact
- Its own M-Pesa payments
- Its own KRA eTIMS invoices
- Its own apps and databases
- Its own team members
- Its own usage limits
- Its own PayEdge shortcodes, where needed
Client billing
Your client pays Eza directly
Set the client’s billing contact when you create their organisation.
Eza sends hosting invoices and M-Pesa payment prompts to that billing contact.
Your client chooses Hobby, Starter or Pro. Prices include VAT at 16%.
| Plan | Monthly price | Good for |
|---|---|---|
| Hobby | KES 1,500 | A small WordPress site or side project |
| Starter | KES 5,000 | Client sites, Laravel apps and early SaaS products |
| Pro | KES 15,000 | Higher-traffic apps and SaaS products with paying users |
Eza issues a KRA eTIMS invoice for each organisation.
Your agency does not need to collect hosting money before Eza renews a client plan.
Your agency access
Keep access without owning the client account
Add agency developers as Members or Admins in a client organisation.
Use roles to control who can deploy apps, view logs, manage domains and change billing.
Every plan includes unlimited team members.
Owners and Admins must use two-factor sign-in.
Read roles and accessWhat you can host
Run client work side by side
Eza Cloud supports common agency workloads in one account structure.
- Laravel and PHP sites
- WordPress single-site and multisite installs
- Node apps and APIs
- Next.js sites
- Python services
- Go services
- Ruby on Rails apps
- Dockerfile apps
- Docker ComposeBeta
Each client organisation can run web apps, background workers, scheduled jobs and persistent volumes.
Managed PostgreSQL, MySQL Beta, MongoDB-compatible Beta, Redis-compatible databases and Eza Object Storage can sit next to the app.
Referral credit
Get credit when a client stays
Refer a client to Eza Cloud and receive referral credit equal to 10% of that client’s hosting plan for 12 months.
The credit applies to the referred client’s plan fee.
Ask about referral credit10%of the client’s plan fee for 12 months
Example agency setup
A clear setup for three clients
Use this as an example layout. These are example client names, not Eza Cloud customers.
| Client organisation | App type | Plan | Billing contact |
|---|---|---|---|
| Juma Bakery | WordPress multisite | Hobby | Client |
| Kilele Logistics | Laravel API | Starter | Client |
| Mtaa Clinics | Next.js web app | Pro | Client |
- Each client receives a separate Eza organisation.
- Each client pays for their own hosting plan through M-Pesa.
- Your agency team can be added to all three organisations without per-seat charges.
Agency workflow
Set up a client in five steps
- 01
Create the client organisation
Use the client’s business name and add their billing contact.
- 02
Invite your agency team
Add developers as Members or Admins.
- 03
Connect the app
Link GitHub, GitLab, Bitbucket or a local project folder.
- 04
Choose a plan
Select Hobby, Starter or Pro. The billing contact pays through M-Pesa.
- 05
Deploy and hand over when needed
Deploy the app, add the client’s domain and transfer organisation ownership when the contract ends.
Agency support
Get help with a client deployment
Every plan includes email support.
Starter and Pro organisations include phone support from Monday to Saturday, 08:00 to 18:00 EAT.
For deployment problems, start with build logs, runtime logs and the troubleshooting guide.
Email support@eza.co.ke for account and billing questions.
FAQ
Agency hosting questions
Something else? support@eza.co.ke
Can I create separate accounts for each client?
Yes. Create one Eza organisation per client. Each organisation has its own apps, databases, billing contact, invoice, limits and team members.
Does each client pay Eza directly?
Yes. The billing contact receives M-Pesa payment prompts and KRA eTIMS invoices for that organisation. Your agency does not need to collect client hosting payments.
Can my agency manage several client organisations?
Yes. Your team can belong to multiple organisations. Every hosting plan includes unlimited team members.
Which client apps can I host?
You can host Laravel, PHP, WordPress, Node, Next.js, Python, Go, Ruby on Rails and Dockerfile apps. Docker Compose is available as Beta for a documented subset.
Do agency clients get phone support?
Starter and Pro organisations include phone support Monday to Saturday, 08:00 to 18:00 EAT. Every plan includes email support.
Put every client on their own hosting account
Create a client organisation, let the client pay Eza by M-Pesa and keep your agency access where it is needed.