Documentation
Freim Deploy is a self-hosted deploy platform. FreimSite is the site template built for it. This page explains what each one does, how they connect, and where the reference lives.
Freim Deploy
A deploy platform for a VDS you already pay for: builds from Git, automatic HTTPS, and a release history you can roll back in about a second. Node 22, SQLite, Caddy and systemd — no Docker, no Kubernetes, and no vendor account watching what you ship.
One panel drives several servers and any number of projects over SSH. Framework detection covers Next.js, Astro, Nuxt, SvelteKit, Remix, Python and plain static output. A deploy starts from a click, a command, or a git push once a webhook is connected.
How to install itFreimSite
The official site template for the platform: an Astro 7 starter, not a page builder. SEO groundwork, islands, zero JavaScript by default, and about twenty content collections defined with Zod schemas — the shape of a page is validated at build time rather than guessed at.
What sets it apart from a generic starter is markup, not tooling. Every block a client might reasonably want to change carries a small data-attribute contract, read and written by a separate app: the CMS portal. Nothing about it asks the client to open a code editor.
Open the templateHow they connect
Neither does much alone: the template is a repository until something builds and serves it, and the platform is a build-and-serve engine until it has something worth deploying. Together they make one path, from a repository to a client editing their own site.
- 01RepositoryStart a site from FreimSite, or point the platform at any repo it can build.
- 02PanelFreim Deploy pulls it, detects the framework, and builds the release.
- 03A live site on its own domainHTTPS is issued automatically; the release goes live once its health check passes.
- 04The client edits it themselvesThey open the CMS portal, click a heading or a price on the live page, and type.
- 05Committed and redeployedThe edit becomes a Git commit and the platform ships it. No code editor, ever, for the client.
Reference
The reference pages live in the public repositories as plain Markdown, English throughout — both halves.
Freim Deploy — the platform
- first-deploy.mdFrom a fresh install to your first site live on HTTPS
- frostdeploy-json.mdThe configuration reference: build, start command, static output, monorepos, python workers, several services in one repository
- environment-variables.mdBuild time versus runtime, which variables reach the build and why secrets do not
- domains.mdPlatform addresses, custom domains, the wildcard record, certificates, www, redirects
- servers.mdAdding more servers to one panel, and what the bootstrap does
- operations.mdUpdates, rollbacks, a site that is down, backups, secrets, uninstalling
- cms-portal.mdThe optional portal where clients edit their own content
FreimSite — the template
- quick-start.mdInstall and run the template locally
- content.mdThe rule behind every content collection: no editable text lives in component code
- cms.mdHow a client edits the site: the markup contract the CMS portal reads and writes
- deploy.mdDeploying the template to Freim Deploy, and why frostdeploy.json keeps its name
- structure.mdThe project's directory layout
Freim Deploy is proprietary; the public repository is its distribution channel: installer, documentation, release artifacts. FreimSite is MIT licensed. github.com/ARTFROST1/FreimDeploy