Upload a ZIP or connect GitHub. The site is live on its own address in seconds, and the client's domain, its certificate and every deploy after it are handled here.
goodsidedental.comgoodsidedental.siteseeker.appIllustrative client site
How a deploy happens
Two ways in and one path after. You never pick a region, size a disk, or keep a web server patched, because there is no box with your name on it.
Step one
Drag a ZIP in, up to 100 MB, or connect a repository and deploy on every push to the branch you pick.
Step two
The framework is detected and built for you. There is no pipeline to write and no command line to learn.
Step three
Served from the network rather than from one machine in one place. Pages cache for an hour, assets for a year.
Step four
Every site gets its own siteseeker.app address the moment it deploys, with HTTPS already on it.
Domains and certificates
Every site answers on a siteseeker.app address the moment it deploys. Point the client's own domain at it and the certificate is issued and renewed for you, with the state visible the whole time it provisions.
On every site, free
goodsidedental.siteseeker.appLive from the first deploy. Nothing to configure.
The client's own domain
goodsidedental.comThere is no TXT record to add. Pointing the domain at us is the proof that it is yours. The exact values appear when you add the domain.
Deployment history
The swap happens last. A deployment builds first, and only a build that finishes replaces what visitors are being served, so a failure leaves the last good deploy answering. Every deployment stays on the list with its own build log, and a failed one can be retried.
#142Push to mainTodayLive#141ZIP uploadYesterdayFailed#140Push to mainMondayReady#139ZIP uploadLast weekReadyBuild log #141
Before the domain moves
A site is reachable on its siteseeker.app address from the first deploy, while the client's domain still points wherever it points today. Send that link, collect the notes, deploy again, and move the domain when they say yes.
Send this
goodsidedental.siteseeker.appPublic from the first deploy. The client needs no account and no login.
Looks great. Let's put it on our domain.
Illustrative client replyWhat you will be hosting
Every one of these needs an address, a certificate and somewhere to answer from. That is the part hosting is for.
Against renting a box
$8
A month, on the smaller plan
| Renting a VPS | SiteSeeker hosting |
|---|---|
| Pick a region, size the disk, provision the box. | Upload the site. There is no box and no region. |
| Install a web server and keep it patched. | The files are served from Cloudflare's network. |
| Issue a certificate, then remember to renew it. | The certificate is issued and renewed for you. |
| Deploy over SSH, or build a pipeline that does. | Drag a ZIP in, or push to the branch. |
| Find out a deploy broke the site when the client calls. | A build that fails never replaces what is live. |
| Keep your own note of what you shipped and when. | Every deployment is listed, with its build log. |
| Read the bill after the traffic arrives. | Storage and bandwidth are a stated cap on the plan. |
Plans
What changes is how many client sites you keep on it. Storage and bandwidth are account-wide caps, stated before you pay.
Two months free with yearly billing.
One or two sites, fully handled.
$8 billed monthly
Included in your plan
Everything a client site needs
Room for the whole roster.
Recommended$15 billed monthly
Included in your plan
$15 billed monthly · Cancel your renewal any time
Everything in Premium, with more room
Before you deploy
What runs here, what does not, and what happens when something goes wrong.
Put the next one up
Upload the ZIP or connect the repository. The address, the certificate and the record of every deploy come with it.
Illustrative client site
