Questions & answers
Straight answers to the things municipalities ask.
No jargon, no dodging. If your question isn't here, ask us directly — we answer plainly.
Ownership & licensing
Owning it, not renting it
Do we actually own the code?
You own a perpetual license to run the version of Munikit you paid for. The source code is delivered to your own git repository — you can read it, modify it, hand it to any developer, or self-host it anywhere. What you're licensing is the right to use and deploy the software; Munikit retains copyright on the underlying product, the same way licensing works for platforms like Craft CMS.
Is the annual renewal a subscription?
No — and this is the difference that matters. A subscription means the software stops working when you stop paying. The Munikit annual renewal ($600/yr) buys you access to future updates and security patches, not the right to keep running software you already licensed. Let it lapse and your site keeps running exactly as it was, on the version you last updated to. Renew again any time to get back on the latest version.
What happens if we stop renewing?
Your site keeps running, exactly as it was. You own the git repository and the PostgreSQL database. You simply stop receiving new versions — nothing breaks, nothing goes dark. Compare that to a subscription platform, where stopping payment means losing access to your own site entirely.
What if Munikit shuts down?
Your site keeps running regardless, because you own the code and the database. Any Next.js developer can take over the codebase — it isn't proprietary. And the CMS underneath Munikit is Payload, an independently-owned, actively-maintained open-source project — not a venture-backed product at risk of being acquired and switched off. Your perpetual license stands on its own.
What if we want to switch vendors later?
Hand the git repository to any developer. Your content lives in a standard PostgreSQL database, not a proprietary format. Any competent Next.js developer can take on the codebase. This is one of the real advantages of the licensing model: you can re-bid ongoing work competitively, because the code is yours to share.
Pricing & hosting
What it costs to run
What does Munikit cost, all in?
A one-time software license of $2,500 per deployment, plus a scoped implementation engagement — typically $15,000–$25,000 for a small municipality, covering custom theme design, content migration, configuration, training, and launch. Optional updates renew at $600/year. A typical small-municipality engagement runs $17,500–$27,500 all-in, versus $55,000–$72,000+ over five years with a subscription platform. See the full pricing breakdown →
What does hosting cost after launch?
For most small municipalities, a modern host's free tier plus a free PostgreSQL tier is sufficient — putting hosting near $0/month. Higher-traffic sites may need a paid tier (around $20/month), and media storage is typically under $5/month. These costs are billed directly to you by the hosting providers; they're not part of the Munikit license, and you control the accounts.
Can it be hosted in Canada, or on our own servers?
Yes. Munikit is a standard Next.js application that runs on any Node.js-compatible host. If your municipality has a data-residency requirement (a Canadian region, for example), a preferred provider, or its own servers, the site can be deployed there. You choose the region and the provider.
Are there any hidden or recurring fees?
No. There's no mandatory platform fee and no annual escalator. The only recurring cost from us is the optional $600/year for updates, which you can decline. Hosting is paid directly to your provider. Any additional custom development beyond the included feature set is quoted and approved before any work begins.
Implementation & support
Getting there, and staying supported
How long does it take to launch?
Most municipal sites launch in 6–8 weeks from kickoff. For comparison, a typical proprietary-platform implementation runs 16–28 weeks. See the step-by-step process →
What if the project runs over time or budget?
We provide a fixed-scope quote before you sign anything — a detailed statement of work specifying exactly what's included and the timeline. If your requirements change during implementation, additional scope is quoted separately before work begins. You won't receive an invoice for work you didn't agree to.
Will you migrate our existing content?
Yes. Content migration from your current site — news, staff, departments, services, meetings, documents — is part of the implementation. You're not left copying and pasting hundreds of pages by hand.
What support is available after launch?
Every implementation includes 30 days of post-launch support. After that, ongoing support retainers are available if you want a dedicated contact for questions and minor changes. If you'd rather hand day-to-day maintenance to a local developer or your own IT staff, the codebase is fully documented and any Next.js developer can take it on.
Can our own developer or agency implement it?
Yes. The license doesn't require you to use our implementation services. If your municipality has an existing web agency or prefers a local developer, they can implement Munikit on your behalf. Get in touch if you'd like a partner referral or developer documentation.
Accessibility & compliance
Meeting the standard
Is a Munikit site WCAG 2.1 AA compliant?
Every component is built and tested to WCAG 2.1 Level AA — the standard required by the DOJ's ADA Title II rule — with an automated accessibility sweep on every page before each release. Accessibility is built in, not an overlay widget or a paid add-on. As with any website, ongoing conformance also depends on the content your staff add, which is why the authoring tools enforce guardrails like requiring alt text on images. More on the rule and the deadlines →
When is our accessibility deadline?
Under the DOJ's ADA Title II rule (as amended in 2026), jurisdictions with a population of 50,000 or more must conform to WCAG 2.1 AA by April 26, 2027; smaller towns and special districts have until April 26, 2028. There is no size exemption. Confirm your specific obligation at ada.gov.
Does it support English and French?
Yes. Every content field supports English and French separately, and missing translations fall back to the default language automatically, so residents never hit an empty page. You can translate content gradually after launch, and French can be kept dormant if your municipality doesn't require it. This also supports French-language obligations such as Quebec's Bill 96.
Still have a question?
Ask us directly. We'll give you a straight answer — and if it's a fit, a live demo and an honest quote for your municipality.
Request a demo