Ship approved content on time, every time
Preview, approve and promote releases between editorial, staging and live environments — on demand or on schedule — and deliver to CDNs, S3 and custom endpoints.
Key features
-
Content delivery
Publish a branch to Amazon S3, FTP, file systems or another Gitana branch, and verify what arrived.
-
Merge conflicts
Conflicts are detected field by field and resolved by rule or by an editor.
-
Scheduled releases
Lock a release to a date, slot in hot fixes, and let it go live on time.
Content delivery
Deploy approved content wherever it is needed, on time: APIs, databases, AI models and custom endpoints around the world.
-
Deployment targets
Publish content from a project branch to one or more deployment endpoints: Amazon S3 buckets, FTP servers, file system locations and other Gitana branches.
-
Reporting and verification
Reports show the state of deployed content, and checksum and path validation find discrepancies. Redeploy to every endpoint in one step.
-
Lifecycle integration
Automatically synchronize content to your endpoints based on how it moves across lifecycles, including content in draft, approved and archived states.
Merge conflicts and conflict resolution
Teams work in their own workspaces without colliding. When the same field changes on two branches, the merge detects the conflict and lets you choose how to resolve it.
-
Rules that resolve conflicts automatically
Set a rule to resolve a type of conflict the same way every time. For example, the latest change can always win.
-
User selects which changes to keep
Editors review each conflict and choose which change to keep: the local change or the change on master.
masterspring-catalog
rights.territories changed on both branches. The differences are marked.["US", "CA"]
Drops EU["US", "EU"]
Drops CA["US", "CA", "EU"]
Keeps bothNext changeset: 44Choose a version to create the merge changeset on master.
Approved changesets can’t be changed. to try another version.
Scheduled releases
Bundle approved contributions into a release and lock in a date. Gitana detects conflicts with releases scheduled before and after yours and helps you reconcile them, so published content stays consistent.
-
Scheduled releases
A release describes a future, locked-in state of your content and goes live on its date.
-
Hot fixes
Push a hot fix ahead of the schedule and see which properties and items it affects in the releases that follow.
-
Go-live actions
When a release goes live it merges and triggers events: email and Slack notifications, and publishing to CDNs, Amazon S3 or other Gitana installations.
Spring 2026Release- Source branch
spring-catalog- Scheduled
- March 2 · 09:00 UTC
- Changesets
42:e9a03f61,43:7c21d0a4- Conflicts
- 1 resolved in
rights.territories - Status
- Approved
- On go-live
- Merge to
master, publish to CDN, notify Slack
Incremental publishing and replication
Changeset versioning records every property-level change, so publishing and replication ship only the delta between branches and endpoints stay in sync.
-
Related content included
When content is published, related items that changed or are missing on the target go with it, such as an article’s images.
-
Synchronized endpoints
Deployment handlers check each endpoint for content that is missing, out of date or misplaced, and ship the fix.
-
Replication between environments
Replication rules push changes from development and authoring to test and live, on a schedule or on demand.
See how Gitana fits your contentSee that merge around your own use case
In a demo, a solutions engineer walks you through Gitana around your use case.In a demo, a solutions engineer walks through a merge like this one around your use case. The same call covers architecture, security, deployment and procurement questions. In a guided evaluation, you work on your own content with one of our engineers on Gitana Cloud.