Svelteload
The stack behind every Nodebrush website. SvelteKit, Payload CMS v3, pnpm monorepo, self-hosted Postgres and object storage. Fast, editable, and maintainable.
What Svelteload is
Svelteload pairs SvelteKit for the public site with Payload CMS for editing, both running on infrastructure we host ourselves. The result is a fast site for visitors, a familiar admin panel for editors, and no per-document fees or vendor lock-in.
What you get
Block-based page editing
Pages are built from reusable section blocks: heroes, banners, image grids, contact forms, and more. Editors drag, swap, and rearrange them without writing code or asking a developer.
Shareable previews
Editors copy a preview link for any draft and send it to anyone, no CMS account required on the other end. Useful for getting sign-off from board members, partners, or clients before anything goes live. Links expire automatically.
Roles and access
Three built-in roles. Admins have full access to the CMS, including settings and configuration. Editors handle the content visitors see (pages, posts, and media) but not backend configuration. Contributors can write drafts but cannot publish. Admins invite new users by email straight from the CMS.
Multilingual content
Every text field can be translated language by language without splitting the site into separate copies. The same page lives in English, Swedish, or any added language, and editors switch between them with a single dropdown.
Built-in search
Pages and blog posts are searchable on the public site, ranked by relevance. No external search service to host or pay for.
Self-hosted media
Uploads are stored on our own object storage and served from your subdomain. No per-gigabyte egress fees, no third-party storage contract, and no surprises on the invoice.
Fast with AI, maintainable without it
Svelteload lets AI assistants move quickly through content work without leaving you a codebase only an AI can maintain. Our Payload MCP wraps the CMS, so compatible assistants read and edit content through typed tool calls rather than being baked into the project. The underlying code stays ordinary, with clean components, typed fields, and normal version control. Drop the AI tomorrow and the site is still readable, editable, and extendable by hand. Everything is backed up and portable, so the whole project can move to your own hosting whenever you decide to take it in-house.
