# klickops > klickops is a Swiss hosting platform (PaaS) operated by Natron Tech AG, a Swiss company in Bern with no US parent, so the US CLOUD Act does not apply. It builds and runs web apps from a Git repository or a container image on servers in Swiss data centres, with your own domain and automatic TLS (from the Hobby plan), managed PostgreSQL with daily backups, and usage-based pricing in CHF with a free plan. Usage beyond the plan comes from a balance paid in first; if it runs out, apps pause after 48 hours instead of an invoice arriving. Projects export as ordinary Kubernetes YAML with no klickops-specific formats. Status: private beta. Access is by waitlist or an access code; there is no open sign-up yet. Operator: Natron Tech AG, Weissenbühlweg 40a, 3007 Bern, Switzerland (https://natron.io). ISO 27001 and ISO 9001 certified. The links below point at the English pages. The German index is at https://klickops.io/llms.txt. The handbook sections cover the product one page at a time: what it is, when to use it, how to do it, every setting, and the limits. Every handbook page is also served as HTML at the same path without the `.md` suffix. ## Product - [What changes when you move to Switzerland.](https://klickops.io/en/alternatives): What changes when your app moves from a US platform to Switzerland: law, currency, database, exit. An honest comparison, including the cases where you should stay put. - [Pricing](https://klickops.io/en/pricing): Free plan with CHF 1 of usage a month, then CHF 9 / 29 / 79 / 199 a month, each including more usage than it costs. - [Host your Claude Code app in Switzerland: step by step](https://klickops.io/en/deploy/claude-code): klickops is a Swiss hosting platform that builds Claude Code apps straight from GitHub and runs them on servers in Switzerland: your own domain from CHF 9, daily backups, free plan to start. - [Host your Lovable app in Switzerland: step by step](https://klickops.io/en/deploy/lovable): klickops is a Swiss hosting platform that builds Lovable apps via their GitHub export and runs them on servers in Switzerland: your own domain from CHF 9, daily backups, free plan to start. - [Host your Bolt.new app in Switzerland: step by step](https://klickops.io/en/deploy/bolt): klickops is a Swiss hosting platform that builds Bolt.new apps via their GitHub export and runs them on servers in Switzerland: your own domain from CHF 9, daily backups, free plan to start. - [Build your first app with AI and put it live, starting from the klickops starter](https://klickops.io/en/guides/build-your-first-app-with-ai): From idea to a running web app with its own URL, without being a developer: take the free klickops starter template, describe what you want to an AI coding tool like Claude Code, and deploy it on klickops with a database and file storage attached. - [Migrate a self-managed PostgreSQL database to klickops](https://klickops.io/en/guides/migrate-postgresql-to-klickops): Move a self-managed PostgreSQL database (on a VM or another host) into klickops managed Postgres: reachability paths, the exact dump-and-restore commands, what happens to your roles and ownership, and a zero-fuss cutover. - [Leaving Heroku for Europe: a practical migration guide](https://klickops.io/en/guides/leaving-heroku-for-europe): How to move a Heroku app to Swiss hosting: what replaces dynos and add-ons, a step-by-step migration path for code, config, Postgres and your domain, and what Swiss jurisdiction actually changes. - [Deploy a Next.js app on Swiss hosting with klickops](https://klickops.io/en/guides/deploy-nextjs-swiss-hosting): A practical walkthrough for running Next.js on klickops: standalone output, deploying from a Git repo or a container image, environment variables, custom domains with automatic TLS, autoscaling, scale to zero and managed Postgres. - [Usage-based billing on klickops, explained](https://klickops.io/en/guides/usage-based-billing-explained): How klickops billing actually works: plan prices that convert into larger usage credits, hourly metering of real consumption, a prepaid wallet instead of an open-ended card, and a worked example with the real meter rates. - [Platform status](https://klickops.io/status) ## Start here - [Your first deploy](https://klickops.io/en/docs/first-deploy.md): From signing up to a running container with a URL, in about five minutes and without touching Kubernetes. - [Organizations, projects, workloads](https://klickops.io/en/docs/concepts.md): The three nouns everything else hangs off, and which one owns what. ## Workloads - [Apps](https://klickops.io/en/docs/apps.md): A container you deploy, scale, and put on a domain. The starting point for everything else in a project. - [Databases](https://klickops.io/en/docs/databases.md): A managed PostgreSQL or Valkey instance that lives inside your project, backed up on a schedule, and reachable from your apps by name. - [Buckets](https://klickops.io/en/docs/buckets.md): S3-compatible object storage for files an app should not keep on its own disk. - [Volumes](https://klickops.io/en/docs/volumes.md): Disk that survives a rollout, mounted into an app at a path you choose. - [Scheduled jobs](https://klickops.io/en/docs/scheduled-jobs.md): A container that runs on a schedule, does its work, and exits. ## Networking - [Domains](https://klickops.io/en/docs/domains.md): A hostname that routes to your app, with a TLS certificate issued and renewed for you. - [Firewall](https://klickops.io/en/docs/firewall.md): Who may reach your workloads, and what they may reach. Deny by default, with three switches that decide the rest. ## Delivery - [Deploying from Git](https://klickops.io/en/docs/git.md): Connect a repository and let klickops build the image, so a push becomes a deploy. ## Operations - [Backups and recovery](https://klickops.io/en/docs/backups.md): Scheduled recovery points for a project, and how to get one piece back without disturbing the rest. - [When something is wrong](https://klickops.io/en/docs/troubleshooting.md): The handful of failures that account for most of them, what each looks like, and what to do. - [Alerts and notifications](https://klickops.io/en/docs/alerts.md): Being told when a workload is in trouble, and choosing where that message lands. ## Configuration - [Secrets](https://klickops.io/en/docs/secrets.md): Values your workloads need and nobody should read back: passwords, API keys, tokens. - [Pull credentials and the build registry](https://klickops.io/en/docs/registries.md): Where klickops gets images it cannot reach anonymously, and where images it builds are stored. ## Organization - [Members and roles](https://klickops.io/en/docs/members.md): Who is in your organization and what each of them may do. - [Plans and costs](https://klickops.io/en/docs/billing.md): What you are charged for, where to see it, and how the plan's limits relate to the bill. - [Getting help](https://klickops.io/en/docs/support.md): Ask the klickops team a question from inside the product. We can already see your projects, so you never have to paste a log. - [Project and organization settings](https://klickops.io/en/docs/settings.md): The two settings pages, what each one changes, and the three actions there is no undo for. ## Tools - [klops CLI](https://klickops.io/en/docs/cli.md): Everything the web interface does, from a terminal or a script. - [MCP server](https://klickops.io/en/docs/mcp.md): Let an AI assistant operate klickops directly, with your permissions and your audit trail. - [API tokens](https://klickops.io/en/docs/tokens.md): Long-lived credentials for scripts, CI and assistants, scoped to a role and optionally to single projects. ## Optional - [Full handbook in one file](https://klickops.io/en/llms-full.txt): every page concatenated. - [Changelog](https://klickops.io/changelog): what shipped in each release.