Uptime, published
Thirty days of stored liveness and dependency probes, including the days that failed.
See current status →
Vilgot Moeschlin builds Tervane.
One person, working in the open. If a build breaks, a bill looks wrong, or a published site goes down, it reaches me — not a queue.
Why this exists
Tools that generate websites are good at demos and bad at the day after. The generated site works until you need to change one thing, find out what it actually deployed, or take your code somewhere else. Tervane is built around the day after: every release keeps its plan, its build checks, its tested version, and its rollback path, and the generated source can be downloaded or pushed to your own GitHub repository whenever you want. Hosted auth, records, and uploads still run on our runtime, so those need their adapters replaced to move — that part is not free, and saying so here is cheaper than you finding out later.
That is also why this site says what it cannot do. The trust center publishes two controls as not attested because no SOC 2, ISO 27001, or independent penetration test has been completed. The examples are labelled hand-designed rather than generated, because they are. A claim you can check is worth more than one you cannot.
What I am accountable for
What shipped, and when
Every user-visible change is written down with the date it went out.
Read the changelog →Security reports
Vulnerability reports get acknowledged within 7 business days.
Read the policy →Company details
Tervane is operated by Vilgot Moeschlin. Full registration, address, and contact details are on the legal notice.