ServiceNow Release Brazil is the next release of the ServiceNow platform, scheduled for the fourth quarter of 2026 — the second in the new era of country names that follows the alphabetical cycle of 26 cities that ended in Zurich (2025) and expands the agency AI agenda initiated in Yokohama and Australia. Early availability is estimated for September and general availability for November, with dates yet to be confirmed in official release notes.
After 14 years of naming versions after cities — from Aspen (2011) to Zurich (2025) —, ServiceNow opened a new era of country-specific naming in 2026. Australia was the first, with general availability on May 5, 2026. Brazil follows, coinciding with direct investment from the manufacturer in the country: ServiceNow opened its first office in Brazil and expanded academic partnerships to train talent in artificial intelligence. As a ServiceNow Elite Partner in Brazil, 4MATT organizes here the complete release history, the expected dates for Brazil, and what the platform's trajectory indicates for the next cycle — with transparency regarding what is official and what is projected.
What is ServiceNow Release Brazil?
The ServiceNow Release Brazil is scheduled for the second half of 2026, succeeding Australia (GA on 05/05/2026). It confirms the new cadence of two major releases per year, now with general availability in the second and fourth quarters — replacing the old Q1 and Q3 schedule — and with upgrade cutoff windows concentrated in June and December.
The dates below were shared by a ServiceNow contributor in an official community forum and are not yet included in published release notes; validation with the ServiceNow account team is recommended before any formal upgrade planning.
| March | Forecast | Degree of confidence |
|---|---|---|
| Early Availability (EA) | Mid-September 2026 | Medium-high |
| General Availability (GA) | Beginning of November 2026 | Medium-high |
From the age of cities to the age of countries: the history of nomenclature.
ServiceNow has used three different release naming conventions throughout its history.
Seasonal era (2008–2010)
The first versions of the platform were identified by season and year: Summer (2008), Winter and Fall (2009), and Spring and Fall (2010).
Age of Cities, Cycle A–Z (2011–2025)
Between 2011 and 2025, ServiceNow released 26 releases in alphabetical order, one for each letter of the alphabet:
| Release | Date |
|---|---|
| Aspen | Dec/2011 |
| Berlin | July 2012 |
| Calgary | Feb/2013 |
| Dublin | Nov/2013 |
| Eureka | May 2014 |
| Fuji | March 2015 |
| Geneva | Dec/2015 |
| Helsinki | May 2016 |
| Istanbul | Jan/2017 |
| Jakarta | July 2017 |
| Kingston | Jan/2018 |
| London | Sept/2018 |
| Madrid | March 2019 |
| New York | Sept/2019 |
| Orlando | Q1/2020 |
| Paris | Q3/2020 |
| Quebec | Q1/2021 |
| Rome | Q3/2021 |
| San Diego | Q1/2022 |
| Tokyo | Q3/2022 |
| Utah | Q1/2023 |
| Vancouver | Q3/2023 |
| Washington DC | Q1/2024 |
| Xanadu | Q3/2024 |
| Yokohama | Q1/2025 |
| Zurich | Q3–Q4/2025 |
Accuracy note: Sources differ slightly on months and years of older releases (for example, Aspen appears as 2011 or 2012 depending on the source). The table uses the historical data consolidated by Infocenter, cross-referenced with the Cyntexa timeline.
Era of Countries (2026–)
With the alphabet exhausted in Zurich, ServiceNow restarted the naming cycle with countries: Australia was the first, followed by Brazil. The change accompanies two structural changes in the release operation: general availability cadence in the second and fourth quarters, instead of the old Q1/Q3, and reinforcement of the N-1 policy, which requires that each instance be, at most, one release family behind the current version.
What to expect from ServiceNow Release Brazil?
Editorial transparency: Brazil's official release notes have not yet been published as of August 7, 2026. The following expectations are derived from the Knowledge 2026 announcements and the trajectory of the Australia release, and will be updated when official documentation becomes available.
| Theme | Expectation |
|---|---|
| Agency AI governance | Expansion of the AI Control Tower (Discover, Observe, Govern, Secure, Measure); a "kill switch" mechanism for agents, resulting from the acquisition of Veza; technical imposition of approved MCP agents and servers. |
| Self-employment | Maturity of Autonomous Specialists (CRM, HR, IT, Security & Risk) in phased rollout, with Otto positioned as the AI gateway to the platform. |
| Headless workflows | Action Fabric — execution of processes between systems via natural language, announced as “coming soon” at Knowledge 2026. |
| Developer experience | Evolution of the Build Agent (GA in Knowledge 2026), consolidation of Workflow Studio, ReleaseOps, and Flow Execution Analysis. |
| Ecosystem | Integration with Microsoft Agent 365; data from Armis and Veza feeding the CMDB; Project Arc (desktop agents, preview with NVIDIA); integration with Lenovo for device intelligence. |
| Platform hygiene | Continued end of support for legacy Performance Analytics, migration to Platform Analytics, adoption of Next Experience on UI16, and hardening of ACLs. |
Market context: why “Brazil”?
The release title is not just a symbolic milestone in the exhausted alphabetical calendar. In 2026, ServiceNow opened its first office in Brazil and expanded academic partnerships to train talent in artificial intelligence in the country, as part of the company's expansion in Latin America. The company's positioning also shifted from "workflow platform" to "AI-first enterprise platform," with intelligence embedded in the infrastructure, not as an optional layer.
Implications for those operating ServiceNow today.
- Plan the upgrade now, not in November. With the N-1 policy, organizations still operating in Zurich need to migrate to Australia or Brazil in the second half of 2026. Treating the upgrade as a semi-annual operational cadence, and not as a one-off project, reduces the risk and cost of regression.
- AI governance is no longer optional. The technical requirement for MCP-approved agents and servers necessitates the design of guardrails before large-scale adoption, especially in regulated sectors such as finance, telecommunications, and the public sector.
- Technical debt accrues interest each cycle. Legacy Performance Analytics, unmigrated UI16, and flows outside of Workflow Studio shorten the useful window for each upgrade; resolving these issues in the Australia cycle generates a concrete advantage when Brazil arrives.
How 4MATT supports the ServiceNow Release Brazil cycle.
As ServiceNow Elite Partner in Brazil, With over 180 certified specialists, 4MATT supports clients in upgrade readiness assessment, migration from Performance Analytics to Platform Analytics, automated regression testing, and governance design for agency AI. Integration of sources such as Armis and Veza is also offered. CMDB This reinforces the importance of a mature configuration database before any automation expansion. For organizations still evaluating their journey on the platform, the material on What is ServiceNow? It provides the context of the fundamentals that underpin these decisions.
Frequently asked questions about the Brazil release.
When will ServiceNow Release Brazil be launched?
A prediction shared by a ServiceNow contributor in the official community points to Early Availability for ServiceNow Release Brazil in mid-September 2026 and General Availability in early November 2026. Official dates will only be confirmed in the release notes published by ServiceNow.
Why is the press release called Brazil?
After exhausting the alphabetical cycle of cities — from Aspen to Zurich, between 2011 and 2025 — ServiceNow began naming releases after countries. Australia was the first, in 2026; Brazil is the second, at a time when the company opened its first office in the country.
What are the main new developments expected in Brazil?
Based on the Knowledge 2026 announcements, expectations include expansion of AI Control Tower, Action Fabric for headless workflows, maturation of Autonomous Specialists and Otto, evolution of Build Agent, and integrations with Microsoft Agent 365, Armis, Veza, and Lenovo. Official release notes for Brazil have not yet been published.
What changes with the N-1 policy of releases?
The N-1 policy dictates that each instance must be, at most, one release family behind the current version of the platform. With Brazil in production, organizations still in Zurich will need to migrate to Australia or Brazil within the June and December cutoff windows, which requires a recurring cycle of pre-reading release notes, regression testing, and change approval.
Is it necessary to go through Australia before migrating to Brazil?
Not necessarily. It's possible to migrate directly to Brazil, provided the N-1 policy is respected during the upgrade. The decision depends on the available testing window, dependencies on custom plugins, and the organization's risk appetite.
What is the new ServiceNow release cadence?
Two major releases per year, with general availability in the second and fourth quarters — replacing the old Q1 and Q3 schedule — and upgrade cutoff windows concentrated in June and December.