Product updates

Establishes a version for a service that had 161 commits and no tag.

The number is new; the software is what has been running.

Customer-visible capability at this tag:

• Workflow inventory, Git-backed approved versions, and drift detection
• Resolve drift in either direction: restore the approved version into n8n, or accept the running version as approved
• Credential storage in a per-customer vault, with forms built from the customer's own n8n; missing and orphaned credential reporting
• Named environments and generated installers (Docker, Kubernetes, Docker Compose, Linux systemd)
• Append-only audit history with export and plan-based retention
• Automatic provisioning from a purchase; verified encrypted export before any data is removed

Known limits at this release:

• Drift is found by scheduled checking, not notification: n8n does not announce an edit, so a direct change is seen at the next check.
• Credential VALUE differences cannot be detected on any automation platform, because none allows a stored value to be read back.
• Changing plan between Individual and Team is not self-serve.

Full notes: CHANGELOG.md

• Where a live workflow no longer matches its approved version, see both sides side by side.
• Resolve the difference in either direction: restore the approved version into n8n, or accept the running version as the new approved one.
• Restoring content never switches a workflow on or off. Its enabled state is left exactly as you set it.
• Once you resolve a difference it stops being reported. Previously an accepted change still showed as outstanding even though it had worked.
• When an action fails, the panel shows what your n8n actually said rather than a bare error label.

• A credential you enter in the panel is delivered all the way into your n8n, sealed at every step.
• If your n8n refuses a credential you are told so, and told that retrying will not help, so you know the value itself needs changing. Previously such a credential said "still saving" indefinitely.
• Non-secret parts of a credential are shown when you edit it, so you only retype what you are actually changing.
• See how many of a credential's fields still need a value.
• The panel tells you when your connector is out of date and how to update it, and will never suggest moving to an older version than the one you run.

• Your activity history now shows what actually changed, and how much, instead of only that something changed.
• Opening the dashboard no longer fills your history with noise. Roughly six in ten recorded events were previously just page loads.
• See at a glance which kinds of activity your workspace has recorded.
• Download the connector for your environment as a single file whatever platform you chose, and the file name tells you which version you have.
• Be told when a workflow needs a credential your n8n does not have — one of the most common causes of a workflow that fails for no visible reason.

• FlowKeyOps finds the credentials your workflows reference, so you do not have to list them yourself.
• Credential forms show exactly the fields your n8n shows — same labels, same hints, same help text — instead of a generic form.
• The form matches the n8n version you actually run, including credential types that inherit their fields from another type.
• Where a field has a sensible default it is offered as a suggestion, so there is less to type.
• See stored credentials that nothing in your n8n uses any more, so you can clean them up.

• Create named environments such as Development and Production, and manage each one separately.
• Get a ready-to-run installer for the environment you are setting up: Docker, Kubernetes, Docker Compose, or Linux systemd.
• Store credentials so that only your own environment can reach them. A credential created in Production is invisible from Development.
• Credential values are sealed before they leave the panel and can only be unsealed by your own environment.
• Run more than one connector for the same environment, so a single machine going down does not disconnect you.
• Retire a connector you no longer use, and it immediately loses access.
• Rename a connector or adjust how often it checks in.

• Connect your own n8n by installing a small connector inside your own network. It reaches out to us, so you open no inbound access.
• What you install is a one-time, short-lived joining code rather than a lasting key: once used it is worthless, so a code left in a ticket or a chat cannot be reused.
• See every workflow in your n8n listed in the control panel.
• Keep an approved version of each workflow, so there is always a known-good copy to compare against.
• Your workflow list refreshes on a schedule set by your plan, and you can also refresh it yourself on demand.
• If your n8n is unavailable, the panel says so plainly rather than silently showing stale information.

• When a subscription ends, an encrypted copy of your data is produced first — and checked that it can actually be read back — before anything is removed.
• That copy is written to two independent places and both are verified, so a single storage failure cannot lose it.
• Your copy is kept for 30 days after your subscription ends, then removed automatically.
• Support can tell you the status of that copy while it is being prepared.
• Your workspace is built and confirmed working before it is marked ready, so you are never handed an environment that is still being assembled.

• Buying a subscription on the website now sets up your workspace automatically, with no wait for someone to do it by hand.
• If a payment confirmation is delivered more than once, your account is only ever changed once.
• Your account keeps a permanent, tamper-evident record of every change made to it.
• How long that history is kept is set by your plan rather than by a fixed rule.
• Cancelling keeps your access until the end of the period you have already paid for, instead of cutting off immediately.

• Your workspace now has a permanent identity of its own, so your data stays yours even as the service grows underneath it.
• The control panel shows your real subscription and workspace details instead of sample values.
• Your workspace is given capacity automatically when you sign up, rather than being set up by hand.
• Capacity another customer has finished with is only reused once it has been confirmed genuinely empty — never on assumption.
• Sign-ins to the panel are short-lived and limited to your own workspace; an attempt to read someone else's is refused.
• A background health check runs continuously and flags anything that looks wrong before it affects you.