Your workloads, running in Morocco
Applications, managed databases, buckets, snapshots and build inputs stay in the Casablanca region. Four capacity tiers, a DPA, and a contract — not a checkout button.
What we claim, exactly
Your data at rest stays in Morocco. That is a country-level statement: the region your resources are placed in is Casablanca, and nothing we run moves your stored data out of the country on its own.
It is about data at rest. Traffic your own application sends abroad, and anything you or your users pull in from elsewhere, is yours to decide — we do not and cannot claim otherwise.
Our infrastructure provider commits in its data processing agreement to keep the data in the region we ordered. Its own documentation names the city, not the building, and it may access data from outside Morocco in order to support and recover the service. We would rather say that here than let you discover it in an audit.
Capacity tiers
A residency region is a small number of machines, so capacity is sold explicitly rather than assumed. Each tier is a memory budget inside the region plus a service count, and the budget is what the platform actually enforces when you deploy.
Maroc Starter
EntryA first regulated workload, or a pilot you have to be able to point at.
- 1,536 MB of memory in-region
- Up to 3 services
- 250 GB of outbound traffic included per month
Maroc Business
A production application with its database and a worker or two.
- 3,072 MB of memory in-region
- Up to 6 services
- 500 GB of outbound traffic included per month
Maroc Scale
Several services, or one that needs real headroom.
- 6,144 MB of memory in-region
- Up to 12 services
- 1,000 GB of outbound traffic included per month
Maroc Dédié
A machine of your own, with nobody else scheduled on it.
- 16,384 MB of memory in-region
- Up to 40 services
- 3,000 GB of outbound traffic included per month
Prices are on top of your Team or Agency plan and exclude tax. Each tier is granted by hand once we have confirmed the region has the capacity, so the figures above are a starting point for a quote rather than a price you can click. Outbound traffic beyond what your tier includes is billed per gigabyte at the Moroccan rate.
What residency covers
- Your application containers, running on machines in the Casablanca region.
- Managed PostgreSQL and Redis instances, and their scheduled backups.
- Object-storage buckets and the snapshots taken from them.
- The source your deployments are built from, which is fetched and built in-region.
What it does not cover
- The claim is country-level and about data at rest. It is not a statement about a particular building, and our provider documents the city rather than the facility.
- Our provider may access data from outside Morocco in order to support and recover the service, as its data processing agreement sets out.
- Anything your own application sends out of the region — an external API, an email provider, a payment gateway — leaves under your control, not ours.
- Some platform features are not available in the region yet: MySQL and MongoDB are not offered there, and services there cannot be put to sleep between requests.
Why it is also faster from here
Serving from Casablanca instead of Europe removes a round trip across the Mediterranean on every request. From a Moroccan connection we measured a 5 ms round trip to the region, against the tens of milliseconds the same request costs from Europe.
Measured from a Maroc Telecom line, with a traceroute that stayed inside Morocco end to end. We publish the method because a latency number without one is worth nothing.
The paperwork
Residency comes with a data processing agreement that states the scope above in contract language, and an invoice in dirham from a Moroccan issuer. If your procurement needs something specific in writing, ask before you sign, not after.
Available on the Team and Agency plans, from 1,200 MAD a month on top of the plan. We grant it by hand after checking the region can take the workload, which is also when we can answer questions a form could not.