About

A website builder that is allowed to leave things out

ClinicSite rebuilds a clinic’s website from the facts that clinic already publishes. The interesting engineering is not in what it writes. It is in what it is forbidden to write.

Why ClinicSite exists

Most independent practices get a website once and then live with it. It was built by an agency, or a relative, or a platform that has since changed hands. Three years later the hours are wrong, a clinician who left is still smiling on the team page, and the whole thing looks dated on a phone. Everyone at the practice knows. Nobody has three weeks and an agency budget to fix it, so it waits.

The obvious modern answer is to point a general-purpose AI site builder at the problem. For a coffee shop that works fine. For a medical practice it is genuinely dangerous. Those tools are built to fill a page. Asked for a team section when they have no staff data, they will produce a plausible clinician with a plausible credential. Asked for insurance, they will list carriers you have never contracted with. Asked for pricing, they will guess a number. Every one of those is a sentence a patient may act on, and a sentence a board may later ask you about.

So the design constraint we started from was not speed or design quality. It was that the system must be able to produce a shorter page rather than a wrong one.

What we build

You can start either way. Paste the address of your current site and we fetch up to three pages of it, then read out the things that are already true: the practice name and description, any JSON-LD the old site emitted, the logo, the theme colour, phone, email, address, opening hours, social profiles and an existing booking link. Or start from nothing at /start and supply those facts yourself.

Generation runs in two phases. The first renders only what sits above the fold, so you can pick a direction in seconds instead of waiting on a whole page you may not want. The second builds the complete site. What comes out is a single self-contained HTML document, not a theme with a database behind it, which is a large part of why the published result is fast and hard to break.

From there you edit visually. The editor is block-based, so headings, sections, images and calls to action are moved and rewritten directly, without touching code. When it is right, you publish to a clinicsite.net subdomain or to your own domain, either bought through us or pointed at us with your own nameservers. Certificates are issued and renewed automatically; there is no SSL step for you to forget.

Two capabilities sit on the Platinum plan and above. The first is a website chatbot grounded strictly in a per-site knowledge base, seeded from your own content at generation time and editable afterwards. It answers from clinic information only, gives no medical advice, and hands off to a human when someone asks for a named person or describes something urgent. The second is EMR integration: connect your practice system and your appointments and clinicians appear in a schedule view in your dashboard. See how it works end to end, or what the output looks like.

How we work

Four decisions that shape everything else in the product.

The generator omits rather than invents

It is instructed, literally and at the system-prompt level, to use only facts drawn from your material, and to drop a section entirely when the facts for it are missing. A page with no team section is a correct outcome, not a failure to handle.

Published sites cannot phone home

Every published site runs under a strict content security policy. Outbound connections are off unless you have configured the chatbot, form submissions are blocked outright, and no third-party scripts, objects or embeds load. A website that collects nothing is a website that cannot leak anything.

Connected credentials are encrypted per tenant

EMR credentials are encrypted at rest with AES-256-GCM, and each ciphertext is cryptographically bound to the clinic it belongs to. The sync itself runs in an isolated worker with its own database role and row-level security, so one clinic’s job cannot read another’s data.

Logs stay free of patient information

Diagnostics are written so that patient-identifying detail never reaches them. It is a constraint on how the system is built, not a promise to redact things later.

The platform runs on Microsoft Azure Container Apps behind a Cloudflare edge. If you want the security posture in more detail before you commit, read what our hosting does and does not do.

What we don’t claim

This is the shortest section on the site and the one we would most like you to read.

Health tech marketing has a habit of implying assurance it has not earned. Compliance badges that certify nothing, uptime figures with no measurement behind them, five-star ratings from customers nobody can name. We would rather be the company you can check.

Things we are asked about, answered plainly.
Capability	Status	What that means
HIPAA certification	Not yet	No such certification exists to hold. We describe the specific technical controls instead, and you can judge them.
SOC 2 report	Not yet	We have not completed an audit. When that changes, the report will be the evidence, not a badge.
Uptime SLA	Not yet	We publish no availability guarantee and no historical uptime figure, because we have not committed to one.
Testimonials and star ratings	Not yet	No quotes, no logos, no review counts anywhere on this site. Everything here is a description of the product.
Review and reputation management	Not yet	Not built. If you need it, use a dedicated tool alongside your site.

Where the gaps are, we put them on the feature page

When the product does not do something yet, that belongs in the same place you go to evaluate the feature, not in a footnote after you have paid. Review and reputation management, for example, is marked as not built on the pages that describe it. If you find somewhere we have failed to do that, tell us and we will fix the page.

Who this is for

ClinicSite is built for independent and small-group practices: the ones without a marketing department, where the website is somebody’s fourth responsibility. Larger organisations with in-house design and a content workflow will find our constraints frustrating rather than useful, and that is a reasonable trade for us to have made.

We work across three broad areas, and each has its own page with the specifics of what a site there usually needs: dental practices, medical practices, and behavioural health and therapy practices. The underlying product is the same in all three. What differs is which facts matter most and which claims are riskiest to get wrong.

You can try the whole generation flow without an account or a card. Previews are deleted after seven days. Publishing requires a subscription, which starts with a fourteen-day free trial and can be cancelled from the billing portal at any time; the details are on pricing.

Reaching a human

Email support@clinicsite.net and a person reads it. There is no tiered queue and no priority lane you can buy, because we have not built one and would rather not pretend otherwise. If you have a question about whether ClinicSite fits your practice before you try it, the contact page is the fastest route, and the FAQ already answers many of them.

Keep reading

See what your clinic site could look like

Paste your current website address. You get a full generated replacement to look at — free, no account, no card.

Rebuild my site free See how it works

Free preview · no card · previews are deleted after 7 days