mapledeploy.ca is built with Next.js, hosted on Bunny CDN.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 15.5.28 | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS1 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks2 | ||
| CDN & Hosting1 | ||
| – | 9 Nov 2026 | |
| Translation & Localization1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
mxext2.mailbox.orgmxext4.mailbox.orgmxext3.mailbox.orgmxext1.mailbox.orgcoco.bunny.netkiki.bunny.netgoogle-site-verification=Zm7gkyLLbD8EUc52NWFy6Ps_Ze_hWcMGvPsXjPYLqv0v=spf1 include:mailbox.org include:md02.com ~allv=DMARC1; p=quarantine; rua=mailto:hello@mapledeploy.caUser-Agent: * Allow: / Sitemap: https://mapledeploy.ca/sitemap.xml
# MapleDeploy > Canadian-first managed Coolify hosting. Git push deploys, managed databases, flat pricing on Canadian infrastructure. ## About MapleDeploy provides managed Coolify instances on Canadian infrastructure. Customers get their own dedicated VM with git push deploys, one-click databases, automatic SSL, and Canadian data residency. Plans start at $45 CAD/month. Starter and Pro plans include a 30-day free trial. ## Key pages - [About MapleDeploy](https://mapledeploy.ca/about): MapleDeploy is a Canadian-owned hosting platform run from Toronto. Learn who builds it, why it exists, and how the business behind it operates. - [Canadian Data Sovereignty](https://mapledeploy.ca/canadian-hosting): Canadian infrastructure for developers who want their data on Canadian soil. Built for PIPEDA compliance, outside US CLOUD Act, GDPR adequate. - [The Canadian SaaS Stack](https://mapledeploy.ca/canadian-saas-stack): A curated list of Canadian and non-US alternatives for building software on sovereign infrastructure. Hosting, email, payments, analytics, and more. - [Coolify MCP server for Claude, Cursor, and Codex](https://mapledeploy.ca/coolify-mcp-server): Let Claude, Cursor, or Codex set up projects, databases, and env vars and deploy your apps on your MapleDeploy server in Toronto. - [Platform as a service in Canada with git push deploys](https://mapledeploy.ca/git-push-deploys): A platform as a service in Canada. Connect your repo, push to your branch, and MapleDeploy builds your app with SSL included. No servers to manage. - [MapleDeploy - The Canadian PaaS with git push deploys](https://mapledeploy.ca/): Canadian app hosting with git push deploys, apps and databases on your own Toronto server, and flat CAD pricing. Try Starter or Pro free for 30 days. - [Report Abuse](https://mapledeploy.ca/legal/abuse): Report abuse, copyright infringement, or illegal activity on MapleDeploy. Instructions for submitting reports and copyright takedown notices. - [Acceptable Use Policy](https://mapledeploy.ca/legal/aup): Acceptable use policy for MapleDeploy hosting services. Covers prohibited content, network abuse, security violations, and enforcement procedures. - [Breach Notification Procedure](https://mapledeploy.ca/legal/breach-notification): How MapleDeploy detects, assesses, and communicates data breaches. Notification timeline and process designed for PIPEDA and Law 25 compliance. - [Canadian Ownership Verification](https://mapledeploy.ca/legal/canadian-ownership): Verification that MapleDeploy is Canadian-owned and operated, with details on corporate structure, infrastructure, and jurisdiction. - [Data Residency Attestation](https://mapledeploy.ca/legal/data-residency): Formal attestation that all MapleDeploy customer data is stored exclusively in Canada, with infrastructure and jurisdictional details. - [Privacy Policy](https://mapledeploy.ca/legal/privacy): How MapleDeploy collects, uses, and protects your personal information. Data handling designed for PIPEDA compliance with Canadian data residency. - [Service Level Agreement](https://mapledeploy.ca/legal/sla): MapleDeploy's uptime commitment, service credit policy, and exclusions. 99.9% monthly uptime target for customer VMs. - [Sub-processors](https://mapledeploy.ca/legal/subprocessors): List of third-party service providers used by MapleDeploy to deliver our service. Includes provider locations and data processing details. - [Terms of Service](https://mapledeploy.ca/legal/terms): Terms of service for MapleDeploy. Covers account responsibilities, billing, cancellation, and service levels. See our SLA for uptime commitments. - [Self-Host 300+ Open Source Apps in Canada](https://mapledeploy.ca/one-click-services): Browse the 300+ one-click services on MapleDeploy, from WordPress and Supabase to n8n and Nextcloud, and deploy them on your own server in Toronto. - [Coolify Managed Hosting in Canada](https://mapledeploy.ca/open-source-stack): Coolify managed hosting you can fully understand. MapleDeploy runs on a stack you can trace: Coolify, Canadian cloud infrastructure, CIRA Canadian Shield. ## Comparisons - [MapleDeploy vs DigitalOcean - managed Canadian PaaS](https://mapledeploy.ca/compare/digitalocean): Compare MapleDeploy and DigitalOcean. A managed Canadian PaaS with git push deploys vs a raw VPS that requires DevOps expertise. - [MapleDeploy vs Fly.io - Canadian PaaS alternative](https://mapledeploy.ca/compare/fly): Compare MapleDeploy and Fly.io. A managed Canadian PaaS with flat pricing vs US-incorporated infrastructure primitives with usage-based billing. - [MapleDeploy vs Heroku - Canadian PaaS alternative](https://mapledeploy.ca/compare/heroku): Compare MapleDeploy and Heroku. A Canadian PaaS with data residency, dedicated resources, and flat pricing vs US-based containers with per-dyno billing. - [MapleDeploy vs Netlify - Canadian PaaS alternative](https://mapledeploy.ca/compare/netlify): Compare MapleDeploy and Netlify. A dedicated Canadian PaaS with flat pricing vs a US-based serverless platform with usage-based billing. - [MapleDeploy vs Railway - Canadian PaaS alternative](https://mapledeploy.ca/compare/railway): Compare MapleDeploy and Railway. A Canadian PaaS with data residency, dedicated resources, and flat pricing vs US infrastructure with per-resource billing. - [MapleDeploy vs Render - Canadian PaaS alternative](https://mapledeploy.ca/compare/render): Compare MapleDeploy and Render. A Canadian PaaS with data residency and flat pricing on a dedicated VM vs US-based per-service billing. - [MapleDeploy vs Vercel - Canadian PaaS alternative](https://mapledeploy.ca/compare/vercel): Compare MapleDeploy and Vercel. A full-stack Canadian PaaS with flat pricing vs a US serverless platform built for frontend frameworks. ## Blog - [All blog](https://mapledeploy.ca/blog) - [Why digital sovereignty matters for Canadian tech](https://mapledeploy.ca/blog/digital-sovereignty-canadian-tech): The case for digital sovereignty at sector scale: cloud concentration, what dependence actually costs, and why the goal is choice rather than self-sufficiency. - [GDPR adequacy: hosting in Canada with EU users](https://mapledeploy.ca/blog/gdpr-adequacy-canada-hosting): Canada's EU adequacy decision removes the transfer paperwork for data sent to PIPEDA-covered organizations. It does not make the GDPR stop applying to you. - [Vertical vs horizontal scaling: most apps only need one](https://mapledeploy.ca/blog/vertical-vs-horizontal-scaling): Vertical scaling means a bigger machine. Horizontal means more machines. What each buys, why one server goes further than you expect, and where the ceiling is. - [How to host a Rails app in Canada](https://mapledeploy.ca/blog/deploy-rails-canada): Deploy a Rails app and its PostgreSQL database on Canadian infrastructure, using the production Dockerfile Rails already generates for you. - [Should your app and database run on the same server?](https://mapledeploy.ca/blog/app-and-database-same-server): Running your app and database on one machine is a normal production setup. What the network hop costs when you split them, and when splitting is right anyway. - [What Canadian app hosting costs in 2026](https://mapledeploy.ca/blog/canadian-hosting-cost): What it costs to host an app in Canada in 2026: flat CAD plans from $45/month, compared with per-service PaaS billing and running your own Canadian VPS. - [PIPEDA and hosting: what the law actually requires](https://mapledeploy.ca/blog/pipeda-compliant-hosting): PIPEDA has no data localization rule. It has an accountability principle, and that changes how you should read any claim about PIPEDA compliant hosting. - [How to deploy a Django app in Canada](https://mapledeploy.ca/blog/deploy-django-canada): A practical walkthrough for deploying Django and its PostgreSQL database on a Canadian server: build config, environment variables, migrations, domain and TLS. - [Where to run managed PostgreSQL in Canada](https://mapledeploy.ca/blog/managed-postgresql-canada): Managed PostgreSQL options with Canadian regions compared, and why running the database on the same VM as your app removes a class of jurisdiction questions. - [Data residency vs data sovereignty: the difference](https://mapledeploy.ca/blog/data-residency-vs-data-sovereignty): Residency is where your data sits. Sovereignty is whose law can compel access to it. The difference, what localization adds, and how to evaluate a host. - [Proof of Canadian data residency: what to ask for](https://mapledeploy.ca/blog/data-residency-documentation-checklist): A client wants proof your data stays in Canada. The documentation to request from your hosting provider, and why a Toronto location alone is not an answer. - [How to run several side projects on one server](https://mapledeploy.ca/blog/run-side-projects-one-server): Run several side projects and databases on one server instead of paying per service. The general answer, what breaks when you consolidate, and how to size it. - [Is AWS ca-central-1 actually Canadian data residency?](https://mapledeploy.ca/blog/aws-ca-central-1-data-residency): AWS ca-central-1 keeps your data in Montreal. That is geography. Jurisdiction is a separate question, and here is when the difference matters. - [Migrating from Heroku to Coolify](https://mapledeploy.ca/blog/migrate-heroku-to-coolify): A practical guide to moving a Heroku app to Coolify. Concept mapping, config vars, Postgres migration with pg_dump, and a safe DNS cutover. - [Self-host n8n on Coolify](https://mapledeploy.ca/blog/self-host-n8n-coolify): Deploy n8n on a Coolify server using the one-click service. Covers domains and SSL, the host and webhook URL variables, owner setup, persistence, and backups. - [Coolify vs Dokploy: an honest comparison](https://mapledeploy.ca/blog/coolify-vs-dokploy): A side-by-side look at two popular self-hosted PaaS platforms. Maturity, service catalogs, multi-server support, and what each license allows. - [Self-hosting Coolify vs managed Coolify: how to choose](https://mapledeploy.ca/blog/self-hosted-vs-managed-coolify): An honest comparison of self-hosted Coolify, Coolify Cloud, and fully managed Coolify hosting. What each costs, what you maintain, and when each fits. - [Coolify vs Heroku vs Railway compared](https://mapledeploy.ca/blog/coolify-vs-heroku-vs-railway): Comparing three deployment platforms from a Canadian perspective. Features, pricing, data residency, and which one fits your project. - [From code to production in 10 minutes with Coolify](https://mapledeploy.ca/blog/deploy-app-coolify-guide): Deploy a web app on Coolify in 10 minutes. Covers Dockerfile vs Nixpacks, port configuration, and custom domain setup with SSL. - [You built it with AI. Now what?](https://mapledeploy.ca/blog/deploy-your-ai-built-project): AI tools are incredible for writing code. But deploying to production still means servers, SSL, DNS, and databases. Here's how to close the gap. - [An experimental guide to technical AEO](https://mapledeploy.ca/blog/answer-engine-optimization-guide): The technical side of AEO: content delivery format, llms.txt, and metadata. Not a content strategy guide, and nobody knows the final playbook yet. - [Building your SaaS on Canadian infrastructure](https://mapledeploy.ca/blog/build-canadian-saas): What makes a product credibly Canadian, and how to assemble a stack that keeps your data out of US jurisdiction. - [Why we chose Canadian-first infrastructure](https://mapledeploy.ca/blog/why-we-chose-canadian-first-infrastructure): Every modern hosting platform runs on US infrastructure. We built MapleDeploy on Canadian and EU providers instead. Here's the full stack and the tradeoffs. - [Law 25 section 17: personal information outside Quebec](https://mapledeploy.ca/blog/quebec-law-25-data-residency): Section 17 requires a privacy impact assessment and a written agreement before personal information leaves Quebec. Toronto counts as outside Quebec. - [Why we use Stripe (for now)](https://mapledeploy.ca/blog/why-we-use-stripe): MapleDeploy keeps your data in Canada, but our payment processing goes through Stripe, a US company. Here's why, and what we offer as an alternative. - [Vercel's hidden jurisdiction risk for Canadians](https://mapledeploy.ca/blog/vercel-canadian-alternative): Zero-config deployments are great until you need to guarantee where your data lives. Why Canadian teams are looking beyond Vercel. - [Railway deploys easily, but your data stays in the US](https://mapledeploy.ca/blog/railway-canadian-alternative): Railway simplifies backend infrastructure, but there's no escaping US jurisdiction. Here's why that matters for Canadian teams. - [Canadian web hosting: what actually matters](https://mapledeploy.ca/blog/canadian-web-hosting-what-matters): Most 'Canadian hosting' is just US companies with a Toronto data center. Here's how to evaluate providers when jurisdiction actually matters. - [The US CLOUD Act: what Canadian businesses should know](https://mapledeploy.ca/blog/us-cloud-act-canadian-businesses): The CLOUD Act lets US courts compel American companies to produce data regardless of where it's stored. Here's what Canadian businesses should know. ## Docs - [All docs](https://mapledeploy.ca/docs) - [Create your server](https://mapledeploy.ca/docs/create-your-server): Create a MapleDeploy account, choose a plan, follow provisioning, and open your managed Coolify server when it is ready. - [Deploy your first app](https://mapledeploy.ca/docs/deploy-your-first-app): Deploy a Git-backed application on MapleDeploy with Coolify. Connect your repository, configure the build, deploy, and verify the result. - [Deploy a one-click service](https://mapledeploy.ca/docs/deploy-a-one-click-service): Deploy a one-click service such as WordPress, n8n or Umami on your MapleDeploy server: find it in Coolify, set its variables, deploy it, and add a domain. - [Custom domains](https://mapledeploy.ca/docs/custom-domains): Point your own domain at a Coolify application on MapleDeploy, configure DNS records, and let Coolify issue SSL certificates. - [Backup guide](https://mapledeploy.ca/docs/backups): Protect your data with automated backups. Set up database backups using Coolify's built-in S3 backup feature with step-by-step instructions. - [Dashboard authentication](https://mapledeploy.ca/docs/authentication): How to sign in to the MapleDeploy dashboard with passwords, social sign-in, passkeys, and two-factor authentication. - [Account recovery](https://mapledeploy.ca/docs/account-recovery): Recover dashboard access after a forgotten password, lost passkey, lost authenticator app, or inaccessible email inbox. - [Organizations](https://mapledeploy.ca/docs/organizations): How MapleDeploy organizations handle roles, invitations, billing access, trials, and shared server management for teams. - [Coolify team access](https://mapledeploy.ca/docs/coolify-access): Set up, reset, and remove Coolify access for organization members so teammates can deploy on the right MapleDeploy server. - [Coolify MCP server](https://mapledeploy.ca/docs/coolify-mcp-server): Enable the Coolify MCP server, create an API token, and connect Claude, Cursor, or Codex to set up, configure, and deploy your apps. ## Full content For published non-legal page content in markdown format, see [/llms-full.txt](https://mapledeploy.ca/llms-full.txt)
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |