v1.1.02026-10-30AddedImprovedFixedSecurity
Four new project types, app deployments from GitHub, and a one-command installer
- AddedFour new project types, fourteen in all: a proxy and reverse-proxy manager, an MCP server and agent manager, DNS and SSL certificate management, and MLOps (GPU inventory, a model registry and serving).
- AddedA one-command installer for Linux, Windows and macOS. Windows and macOS run it through Docker Desktop. It checks requirements and ports and asks instead of failing, and can install Docker on Linux. It also installs on a new cloud server from its start-up script, and --eval tries Talos on your own computer, with one command that removes every trace again.
- AddedDeploying applications from GitHub: pick a repository from the GitHub App installation, with every environment variable the repository reads offered for you to fill in. Each app gets its own page and URL, live build logs, and the reason a failed build failed. Docker is installed on the server when it is missing, the build stops before the server runs out of memory or disk, apps can pull from private registries, and a database can be created on one of seven engines alongside an app.
- AddedVisual planners: draw cloud infrastructure, a Kubernetes cluster or a Docker Compose stack on a canvas, review the generated plan, then apply it.
- AddedConnect a Terraform repository and plan it through the job queue, with scheduled drift detection. A saved plan is applied only after review. Terraform runs in a separate runner container, never in the backend, and terraform init cannot run code the repository chooses.
- AddedAWS: security posture checks, compliance mapping and change history. Every check reports passed, failed or not evaluated, with the reason, so a check that could not run never reads as clean.
- AddedGetting-started guidance for every project type, shown above the dashboard, and feedback when work you queued finishes.
- ImprovedForms open as a drawer beside the page, and a dropdown that needs an asset (a server, a key) can create it in place. Asking Talos opens over the page you are on instead of navigating away.
- ImprovedRunning the install command again is a safe way to start a stopped Talos. It says whether it will only start Talos or upgrade it, names both versions before an upgrade, never moves an install to an older version unless you ask for one with --version, and finds an install in a custom folder after docker compose down.
- FixedLive log streams were refused for every job; they now connect.
- FixedA rate-limited request (429) signed people out. Only an expired or invalid session (401) does now.
- FixedAdopting an existing cloud resource into a canvas could remove its tags.
- SecurityA self-hosted install’s first account is guarded by a one-time setup token. The installer generates it and shows it with the link, so someone who finds the address first cannot claim the install.
- SecurityClosed a command-injection path through an app’s root directory, Dockerfile path or output directory, and stopped Talos secrets from reaching Terraform provider processes.
- SecurityA Viewer could read security findings through the audit log. Findings now follow the same permissions everywhere.
v1.0.12026-08-05AddedFixed
amd64 images and first-install fixes
- Addedlinux/amd64 images. 1.0.0 published arm64 only, so on most machines the install stopped at "no matching manifest for linux/amd64" before anything started. Both architectures are now in every published tag.
- FixedA brand-new install could not create its first account from a browser. The login page offered only "contact your organization admin for an invite", on an install that has no admin, no invite and no organization yet. It now shows a "Create a workspace" link while no organization exists, and hides it again once one does, so a fresh install stays claimable exactly once.
- FixedThe documented way to generate the database password produced passwords that broke the install. `openssl rand -base64 24` emits "/" and "+", and that value is substituted into a connection URL where a "/" ends the authority section, so the backend restarted repeatedly on "invalid port number in database URL", a message that never mentions the password. The instructions now generate URL-safe hex, and the backend stops with an explanation and the command to fix it instead of that error.
- FixedPinning a version as TALOS_VERSION=v1.0.1 failed with "manifest unknown". The release is named v1.0.1 but the image tag carries no "v", which made the wrong value the natural guess. The correct form is documented alongside the variable.
v1.0.02026-08-04AddedSecurity
First public release
- AddedA published Docker Compose install: two generated secrets and a database password, one command, no source checkout, no registry login and no account. The images are public.
- AddedAgentless server management over plain SSH. Nothing is installed on the machines you manage, and read-only discovery reports OS, kernel, runtimes, containers and database engines without changing anything.
- AddedTen project types from one control plane: bare servers, Frappe/ERPNext, Docker, Kubernetes, application deployments, databases, hypervisors, and AWS, Azure, GCP and Oracle.
- AddedEvery action runs as a queued job with live log streaming, and what you watch is exactly what lands in the audit ledger.
- AddedBackups with verified restores (a backup is only marked verified after it has actually been restored into a temporary instance and checked), plus point-in-time recovery for managed Postgres and tiered retention per database.
- AddedDestructive operations are plan-then-apply: you see exactly what will be destroyed, and how each item was identified, before anything runs. A server reset requires a verified backup first.
- AddedAn optional AI engine on your own API key, across multiple providers. It cannot act directly: it writes a proposal, a human reviews the exact diff, and only on approval does the work enter the same job queue a human would have used. No model provider is contacted unless you configure one.
- AddedPer-project dashboards, scheduled reports, and a read-only assistant for asking questions about your own fleet without granting write access.
- SecurityThe backend refuses to start on a missing or published-default JWT_SECRET or ENCRYPTION_KEY, before it opens a network connection, rather than warning and continuing with a signing key that is published in a public repository.
- SecuritySSH keys, cloud credentials and database passwords are encrypted at rest under your ENCRYPTION_KEY, decrypted in memory only for the duration of a job, and never written to a log line or a job payload.
- SecurityPer-resource permissions are enforced on visibility, proposal, approval and execution independently, and every route is organization-scoped. The control plane itself is not indexable and serves no public page; the first thing it presents is a login form.
- AddedOne switch selects self-hosted or multi-tenant mode against a single shared schema, so the isolation a hosted deployment relies on is the same code a self-hosted install runs.