What we're building next.
These are the features we've prioritized to ship, in order — number one is what ships next. This list is hand-maintained; it's a statement of intent and priority, not a dated commitment, and the order can change as we learn.
Already shipped? See the changelog for everything that's live.
Unbundled subscriptions — turn on features à la carte
We're replacing plan gates with simple add-ons, so you switch on exactly the features you want without having to jump a whole tier to reach one of them.
Usage-based billing and a Starter sandbox
Pay for what your projects use, and start in a sandbox with a monthly allowance of usage included. Heavier apps can run for a limited time before you commit to a plan.
Git watched paths
Tell a project which paths in your repository it depends on, so a push triggers a build only when files that actually matter to it change — the foundation for clean monorepo deploys.
Local AI — run open models and serve your own endpoints
Run open-weight models on Canadian infrastructure and expose your own code as inference endpoints, with no data leaving the country.
Better email classification and opt-out controls
Clearer categories for the mail we send and finer opt-out controls, so you hear from us about exactly what you care about — and nothing else.
Custom log and audit policies, with self-serve export
Set your own retention policies for runtime logs and the audit log, and export either one yourself, whenever you need it.
A trust and compliance page
One page that answers what security and privacy reviewers ask: our subprocessors and where they are, who can access your data, breach notification, retention and deletion, uptime and maintenance, and how to leave with your data.
Blue/green deployment slots for managed and staging releases
Ship to a staging slot, then promote to production with an instant swap — with the option to hold a failed deploy so a broken build never replaces a working one, even when you're running a single slot. A shutdown window you can set lets the old version finish its long requests before it stops.
Preview deploys with their own database
Preview deploys can run against a separate copy of your database instead of sharing production's, so testing a pull request never touches real data.
Self-serve domain transfers
Transfer a domain in or out yourself, right from the dashboard, without contacting support.
Export everything in one step
Download your databases, files, environment variables, and project settings together as one archive, so leaving Canner is a single step and you always hold a complete copy.
Best-in-class native monorepo support
Run several apps from one monorepo inside a single project, sharing the same project resources. We think we can make this the best monorepo experience anywhere.
Rotessa EFT payments
Pay by pre-authorized bank debit (EFT) through Rotessa, a Canadian payment processor — an alternative to paying by card.
Outbound email sending for your app
Send transactional email — invoices, receipts, notifications — straight from your app on Canner, without wiring up a third-party provider yourself.
Declarative project configuration and background processes
Describe your services, databases, and resources in one config file instead of clicking through the dashboard for each piece — including a background worker that runs beside your web app in the same project, with the same code, database, and variables. The same file works for review, version control, and repeatable setup.
Managed queues
A hosted message queue that pairs with Worker projects, so background jobs can pick up work reliably instead of you wiring up your own queueing layer.
Lightweight serverless functions
Deploy a single-file endpoint alongside your full apps and Workers, for the cases where a whole app is overkill and a scheduled job doesn't fit either.
Private container registry
A per-organization registry for image-based deploys, for teams whose workflow is Docker-first rather than git push.
One-off commands and a shell for your project
Run a command once inside your project, with its own environment — a data import, a fix-up script — and get the output and exit status back. It runs as your project, on Canadian infrastructure.