Implementation BlueprintExecution layer

sitesolide Internal Tools Hosting Offer (6-9 days)

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. Time: 6-9 days.

By InnovaAI ResearchPublished

DevOps Automation

How do you implement it?

Blueprint

sitesolide Internal Tools Hosting Offer (6-9 days)

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.

Prerequisites
  • Client agrees to own and pay for a Debian 13 server (for example a Hetzner instance) plus a domain with a DNS zone the agency can edit
  • Client identity provider access: Google Workspace, Microsoft Entra, Okta, or a generic OpenID Connect app registration
  • A named client-side owner who will hold server credentials and approve security patching windows
  • Inventory of the small apps, dashboards and prototypes to migrate, with their runtime (static, Bun, Node)
  • Agency engineer who is comfortable with systemd, Caddy and CLI operations, since sitesolide is MIT-licensed software you operate yourself
Execution Timeline
  • 1.Provision the Debian 13 server and point a Cloudflare-managed domain at it with a wildcard DNS record for subdomains
  • 2.Install the sitesolide single binary and confirm the CLI responds before any client app is touched
  • 1.Run `sitesolide deploy` on one static site and one Bun/Node app to validate HTTPS issuance through Caddy and systemd service creation
  • 2.Verify subdomain routing resolves per app and that restarts survive a server reboot
  • 1.Connect the client's Google Workspace, Microsoft Entra, Okta or OpenID Connect provider so private dashboards sit behind company sign-in
  • 2.Configure per-app sharing by email or domain and issue scoped, revocable team tokens for client staff
  • 1.Declare background workers and scheduled jobs in sitesolide.json for the pilot app
  • 2.Confirm hourly backups run and that a restore of one app has been tested end to end
  • 1.Migrate the remaining dashboards and prototypes from the inventory onto the server
  • 2.Set up minute-level monitoring alerts and route them to the agency on-call channel and the client owner
  • 1.Wire the MCP server so AI agents can read deployment status, logs and access records during support
  • 2.Write the runbook covering deploy, rollback, token revocation and backup verification
  • 1.Handover session with the client owner: CLI basics, patch cadence, and who calls whom during an outage
  • 2.Sign off the definition of done and start the operations retainer
$1,800 fixed setup for the Starter Deploy scope (16h), scaling to roughly $4,500-$7,000 for the full multi-app migration; software cost is $0 because sitesolide is free MIT-licensed software, with the client carrying only server and domain spend6-9 days
ROI Logic

sitesolide carries no licence fee, so the entire setup fee is margin against engineering hours: a $1,800 Starter Deploy at 16h of work clears roughly $112 an hour before server costs, and the multi-app scope lands higher because the SSO, worker and backup configuration is reused rather than rebuilt. The recurring operations retainer is the real return, since hourly backups, minute-level monitoring and scoped tokens mean the agency monitors one server instead of chasing per-seat SaaS renewals for the client.

Deliverables
  • Configured Debian 13 server running sitesolide with HTTPS, subdomain routing and systemd services verified
  • SSO integration record showing the connected identity provider, per-app sharing rules and issued scoped team tokens
  • sitesolide.json manifest listing workers and scheduled jobs for each deployed app
  • Backup and monitoring handover pack: hourly backup schedule, tested restore, and minute-level alert routing
  • Operations runbook covering deploy, rollback, token revocation and patch cadence
Definition of Done

Every app in the client inventory deploys via `sitesolide deploy` to its own HTTPS subdomain behind company SSO, with a tested hourly backup restore and monitoring alerts reaching both the agency and the client owner.

Open the sitesolide coursesitesolide decision recordBrowse the Academy

More on sitesolide

More for DevOps Automation