Maple Open Tech · Services

Hugo Sites

Static sites that build in seconds and serve in milliseconds — with no database to patch, no admin login to defend, and hosting costs that round to nothing.

Start a conversation See all services

Hugo Sites

What a hugo sites engagement includes

A site that does not need a server to render a page does not need a server to be attacked. For anything that is published rather than transacted — a brochure, a documentation set, a catalogue, a campaign — static is faster, cheaper and quieter to own.
  • A content model your team can edit, in Markdown or through a Git-backed editor
  • Builds measured in seconds, so a correction is live before the meeting ends
  • No database and no admin panel, which removes most of a site’s attack surface
  • Accessibility verified at build time, not audited after launch
  • Hosting anywhere — a CDN, a Canadian host, or a machine you already own

Talk through your project

What this looks like in practice

  • Hugo Sites — illustrative

    Documentation set

    Versioned, searchable, edited alongside the code

  • Hugo Sites — illustrative

    Brochure site

    A dozen pages, verified contrast, perfect scores

  • Hugo Sites — illustrative

    Migration from WordPress

    Every url preserved, redirects generated

How it runs

  1. 01

    We look at what you publish

    How often it changes, who changes it, and what actually needs a database. Sometimes something does, and we will say so.
  2. 02

    We build the content model

    The shapes your pages come in, so writers fill in fields rather than fight a layout.
  3. 03

    We migrate and verify

    Every old url either answers or redirects, and we check every one of them rather than assuming.
  4. 04

    We hand over the pipeline

    A build anyone on the team can run, and a deploy that is one command or one merge.

Questions people ask

Can non-technical people edit a static site?
Yes. Editing is a form in a browser, backed by Git rather than a database. What they lose is the ability to break the layout; what they gain is a full history of every change.
What if we need a form, or search, or comments?
All of those work — they just run as a service rather than inside the page. Search can even be built into the site at compile time.
Is this only for small sites?
No. Static generators handle tens of thousands of pages. The constraint is how often the content changes, not how much of it there is.

Want to talk about sovereignty?

Tell us what you run, where it runs, and who can reach it. We will tell you honestly what moving it to Canadian infrastructure would take.