Confluence Long Term Support is an Atlassian release track for self-managed Data Center deployments that pairs a stable Confluence version with two years of critical bug and security fixes, letting organisations document, plan and share knowledge without constant upgrades.
Confluence Long Term Support is a release designation, not a separate product. It applies to specific Confluence Data Center versions that Atlassian marks as enterprise-ready: the platform where teams write pages, build spaces, attach files and map out project knowledge in one searchable workspace. Choosing Confluence Long Term Support changes your upgrade rhythm rather than your day-to-day work. Instead of tracking every feature release, administrators deploy an LTS build and stay on it while teammates author documentation, run meeting notes and link pages to tasks. The purpose is straightforward — keep collaboration tools stable and predictable while still receiving the fixes that matter most.
Adopting Confluence Long Term Support usually starts with a compatibility review. Teams check that their database, operating system, identity provider and marketplace apps are all certified against the chosen build, then rehearse the upgrade in a staging copy before touching production. Because the support window is long, that homework is done once instead of every few months, which suits regulated industries and anyone running a heavily customised instance. It also benefits mixed environments: a team such as Quba can keep a shared knowledge base online while deliberately delaying feature upgrades that would otherwise force retraining and re-testing. The trade-off is that new features arrive later, so the decision comes down to how much your organisation values predictability over novelty.
The clearest benefit of Confluence Long Term Support is predictability. Administrators plan a single migration, validate it, and then run the same build for two years while receiving critical bug fixes and security patches, which removes the annual scramble of testing every feature release and re-certifying plugins. Stability compounds elsewhere: support agreements, audit evidence and internal training material stay valid for longer because the interface and APIs stop shifting underneath them, and security teams get a defined window in which patches will still land. Editorial and operations teams keep their spaces, page trees, macros and templates intact, so accumulated documentation remains useful rather than being rebuilt. Fewer unplanned upgrades mean fewer surprise outages and less disruption for staff who depend on the workspace daily. The result is a documentation platform that behaves like dependable infrastructure — slow to change by design, but reliably available when teams need to find an answer or publish a decision.
Key capabilities and highlights.
Confluence Long Term Support keeps a designated version inside a two-year maintenance period, delivering critical bug fixes and security patches long after ordinary feature releases have been retired. Administrators gain a realistic upgrade schedule and a stable target for testing, rather than a rolling treadmill of quarterly migrations.
Marketplace vendors publish compatibility against long term support builds, so administrators can confirm that plugins, macros, diagramming tools and integrations are properly supported before migrating rather than discovering breakage afterwards. That certification reduces last-minute surprises during a production cutover and shortens the period in which core collaboration workflows are unavailable to the people who depend on them.
Confluence Long Term Support lets you move between supported builds on your own timetable. Planning, budgeting and rehearsing one migration every couple of years costs far less than absorbing a new feature release each quarter, and it frees platform teams to work on integrations, governance and content architecture instead of perpetual upgrade testing.
Confluence Long Term Support is aimed at self-managed Data Center installations, so the track suits clustered, high-availability setups that serve thousands of concurrent users and cannot absorb unscheduled downtime. Load balancing, node sizing and disaster recovery plans stay valid for longer, letting infrastructure teams invest in capacity and monitoring rather than repeatedly revalidating a new topology.
Interface behaviour and REST endpoint contracts change far less often between long term support releases, which keeps custom scripts, automation pipelines and embedded dashboards working without repeated rework. Teams can build reporting, provisioning and content migration tooling on a foundation that is not quietly repositioned every few months.
The longer service window of Confluence Long Term Support makes it easier to evidence patch currency to auditors, map security fixes to internal controls and keep risk registers accurate across multi-year projects. Fewer version changes also mean fewer policy documents, standard operating procedures and staff training materials that need rewriting mid-cycle.
Supported upgrade paths and end-of-support milestones are published well in advance, so administrators know exactly when a build retires and which version to target next. That foresight turns a migration into a planned project with a budget line, rather than an emergency response triggered by a support notice.
Spaces, page hierarchies, templates, labels and macros stay put for longer, letting accumulated team knowledge keep its structure and remain searchable instead of being rebuilt after every upgrade. Editorial owners can maintain a coherent knowledge base over several years without reworking navigation, permissions or content conventions each time the platform moves forward.
Browse historical releases and previous builds.
Common questions about Confluence Long Term Support.
It marks specific Data Center versions that Atlassian maintains with critical bug fixes and security patches for roughly two years. Standard feature releases stop receiving those fixes after about six months, so an LTS build is the conservative choice for production.
No. It is the same collaboration and documentation platform; only the release designation and maintenance commitment differ. You install an LTS version and use spaces, pages, permissions and search exactly as before.
Each LTS build is supported for two years from its release. Roughly one new LTS version appears per year, so there is usually an overlap period in which two supported builds exist and migration can be staged.
Temporarily, yes. Features introduced in intermediate releases arrive later, once they are folded into a future build. The trade-off is that those features get more time to stabilise before your organisation adopts them.
It suits regulated, heavily customised or high-availability environments where predictable maintenance matters more than early access. Teams that want the newest collaboration features as soon as they ship may prefer the regular feature release cadence.
Review compatibility for your database, operating system, reverse proxy and marketplace apps, take a full backup, and rehearse the migration in a staging environment before scheduling production downtime.
Security patches and bug fixes stop, so remaining on it increases exposure over time. Administrators should plan the move to the next supported build well before the published end-of-support milestone.
LTS releases are published for Data Center deployments, while the cloud offering follows a continuous update model instead. Self-managed teams that already run Data Center can adopt an LTS build whenever their current version approaches end of support.
Confluence Long Term Support is an Atlassian release track for self-managed Data Center deployments that pairs a stable Confluence version with two years of critical bug and security fixes, letting organisations document, plan and share knowledge without constant upgrades.
Evernote is a note-taking and information management app that organizes written notes, documents, web clippings, and tasks into a searchable workspace for research, meeting records, and ongoing projects.
Notion is a workspace application that combines notes, documents, databases, and project tracking, helping individuals and teams organize information, maintain shared knowledge, and coordinate work through connected pages.
印象笔记 is a cross-platform note-taking and knowledge management app that captures text, web clippings, images, audio and files, keeps them tagged and searchable, and syncs everything across desktop, mobile and web.
Freeplane is a mind mapping application for building, organising, and navigating ideas as a hierarchy of nodes. It is used for planning, note taking, and knowledge work where maps need notes, attributes, formulas, and filters rather than a simple picture.
Comments