sitesolide

sitesolide is MIT-licensed and runs on a Debian 13 server the agency already pays for, so every internal dashboard or AI-built prototype you deploy adds zero per-seat SaaS cost. The verdict is blunt that resale potential is limited, which means the return comes from cutting your own delivery friction, not from a white-label retainer. Agencies that treat it as internal infrastructure compound margin quietly; agencies that keep buying hosted seats per project keep paying monthly for the same outcome.

Pipeline Portability Premium is the pricing value an agency retains when its delivery automation can be moved between hosts without a rebuild. The framework treats every pipeline as two assets: the logic (build steps, test gates, deploy order) and the binding (the specific platform's config format, secrets store, and hook syntax). Logic travels; binding does not. Agencies that keep the binding thin can re-host a client stack in days, which matters when a client demands a private cloud, a regional data residency rule, or a cheaper provider mid-retainer. The premium shows up as faster onboarding, fewer renegotiation losses, and the ability to quote migration work as a billable line rather than absorbing it. A YAML manifest that starts services in dependency order, like systemg, or a Git-triggered deploy that targets any SSH server, like DeployHQ, keeps the binding thin. A platform whose config only runs on that platform thickens it.

Portability Premium is the price an agency pays, in migration hours and client disruption, for every layer of its delivery pipeline that cannot be lifted out and moved to another provider. It reframes stack selection: the question is not which CI/CD or hosting tool deploys fastest, but how much of the client's release process survives a forced exit. A pipeline built on Git-triggered deploys to any SSH server travels cheaply; one wired into a single vendor's proprietary build steps does not. The premium compounds across a retainer portfolio, because each client adds another environment to re-plumb. The same logic now applies to agentic layers: MCP servers can silently rewrite the instructions an agent follows after approval, so an automation chain can drift without anyone on the delivery team signing off. Agencies that price portability into architecture decisions keep negotiating room on hosting and inference costs as client compliance demands shift.

Compliance Perimeter Drift is the gap that opens when an agency's standardized automation stack stops matching the regulatory or data-residency perimeter of a specific client. The framework says the perimeter, not the tool, is the unit of standardization: agencies should map each client's compliance boundary first, then decide which pipeline stages can stay on shared infrastructure and which must run inside a client-controlled environment. The drift is invisible until an audit, a breach, or a procurement review exposes it. For agencies, the cost is not the tooling swap itself but the re-certification, re-documentation, and re-testing that follows a late discovery. A concrete signal: researchers used Claude Opus 4.8 and 5 to breach OpenAI's GitHub repository in under 72 hours, which shows how quickly code-adjacent systems become an attack surface when access boundaries are assumed rather than enforced. Agencies running shared CI runners across clients should treat that assumption as a perimeter risk, not a convenience.

Adopt sitesolide only when server ownership and patch responsibility sit with someone on your team, and treat it as internal infrastructure rather than a billable client product.

Standardize the automation stack only after you have priced the cost of leaving it for your three largest clients.

IF your agency already runs (or will run) a Debian 13 server you control and needs small apps, dashboards, and AI-agent-built prototypes behind Google Workspace, Entra, Okta, or OpenID Connect sign-in, THEN sitesolide is a buy-or-adopt decision at the cost of the server plus your own operations time, since the software itself is free and MIT-licensed. IF you have no technical staff to patch that server and operate the single-binary CLI, or you need a client-facing white-label hosting product, THEN skip it: sitesolide is infrastructure tooling for your own delivery team, not a resale platform.

Agencies stand up a client-owned Debian 13 server running sitesolide so a client's dashboards, prototypes and internal apps ship behind company SSO with hourly backups and minute-level monitoring, billed as a fixed setup fee plus a server operations retainer.