The cost you are not invoicing
A small agency ships a lot of small sites. A landing page for a campaign. A one-pager for a launch. A brochure site for a client who does not need a CMS.
None of them are technically hard. They are all technically annoying, in the same small ways every time — a hosting account somewhere, DNS records, an SSL certificate, a login handed to someone.
Twenty minutes per site does not look like a problem. Twenty minutes across forty sites a year, in a team where only one person can actually do it, is a bottleneck with a salary attached. And none of that time appears on an invoice.
What changes
Not one account per client, not a spreadsheet of logins. Every site you manage, in one list.
One subscription covering every site you run, rather than a scattering of small charges across a dozen providers that someone has to reconcile each month.
A client site on a generic subdomain looks unfinished. Every plan connects real domains, with SSL issued automatically.
No terminal, no Git, no repository. The designer who built the page can put it online without waiting for the one person who knows the deployment setup. Note that at launch the account is shared rather than seat-based — see the questions below.
Where this fits — and where it does not
Being direct about this saves you an evaluation.
Landing pages, campaign microsites, brochure sites, one-pagers, client deliverables, event pages, pitch sites, anything a designer finished and that needs to be live.
Sites needing a CMS a client edits themselves, e-commerce, user accounts and logins, anything with a database, anything requiring server-side code.
sofast serves static files. It does not run code. If your client needs to edit their own copy weekly, they need a CMS and this is not one.
The handover question
The objection that comes up in every agency evaluation: what happens if a client wants to take their site elsewhere?
They take it. Your files are downloadable from the dashboard at any time, as the same folder you uploaded. There is no proprietary format to convert out of, no export fee, and no notice period on the files themselves. The domain belongs to whoever registered it, and repointing its DNS records takes minutes.
This is worth knowing before you commit, not after. An agency that cannot promise a clean handover has to avoid the conversation with clients, and that is a bad position to argue from.
How domains connect →What it costs against what it replaces
Most agencies are already paying for hosting — often a reseller plan, a shared host, or a per-client account somewhere. The comparison is not against zero.
The comparison worth running is the internal one. Take your last ten small sites. How long did each take between "the design is finished" and "the client has a live link"? Multiply by your billable rate. That number is what the tooling costs you, and it does not appear anywhere in your accounts.
See the plans →Common questions
Yes, and this is the normal arrangement. You need access to their DNS panel, or you send them two records to add. The domain stays registered in the client's name, which is usually what both sides prefer, and the site runs on your account.
Not at launch. Sites live under your account and clients do not get their own login. In practice that means you publish updates on their behalf, which is how most agencies work with brochure sites anyway. If a client needs to edit their own content, they need a CMS and this is not one.
No. The dashboard is sofast-branded and there is no reseller mode. What your clients see is their own site on their own domain, with nothing on it pointing back here — the branding question only applies to the dashboard, which they do not have access to.
The site is on your account, so you control it. You can take it offline, hand over the files, or leave it running. Nothing is tied to the client's payment method unless you set it up that way.
Starter covers 2 sites, Pro covers 10 and Large covers 30. Check that against your actual portfolio rather than your current one — small client sites accumulate faster than agencies expect, and a studio shipping a landing page a month crosses 10 within a year.
See the plans →Not with separate logins at launch. There are no seats and no per-user permissions, so a team shares one set of credentials. For a studio of three to six people that usually works, but it is worth knowing before you build a process around it. Named seats are on the roadmap and not shipped.
Static sites handle traffic far better than dynamic ones, because there is no database and no code running per visitor. A campaign page that goes unexpectedly well does not fall over.