Qonda Deploy gives GIS teams version control, approval workflows, and a full deployment history for ArcGIS Enterprise and ArcGIS Online content - all from a single web interface.
An example Qonda Deploy pipeline - from DEV snapshot to PROD in four controlled stages
Works with your ArcGIS stack
If your team manages ArcGIS content across more than one environment, these questions come up constantly. Qonda Deploy answers all of them.
From snapshotting portal items to full approval workflows and a searchable deployment history, Qonda Deploy gives your team a complete release management platform for ArcGIS content.
Register ArcGIS Portal items - web maps, apps, dashboards - and manage its deployment lifecycle from a central catalog.
Capture the current state of any portal item as a named version. Every snapshot records who took it and when, giving you a complete version history for each item.
Compare any two versions of an item side-by-side with a full JSON diff. See exactly what changed - down to individual field values and nested configuration.
Register DEV, TEST, STAGING, and PROD environments. Promote any item version to any target with a single action - no scripting required.
Require one or more approvers before a deployment reaches a sensitive environment. Assign approval groups per environment and track every decision with a timestamped audit record.
Automatically translate URLs, service references, field names, and domain values between environments so item configuration is correct after promotion - no manual editing needed.
A real-time view of in-progress deployments, approvals awaiting action, and recent activity. Spot issues the moment they occur - not after the fact.
A complete, searchable record of every deployment. Filter by item, environment, user, or date. Re-deploy any historical version at any time with a single click.
Scheduled daily and monthly database backups with DOW rotation run automatically in the background. Manual backups can be triggered from the settings UI at any time.
Every login, failed login, deployment, approval, and configuration change is logged and visible to administrators. Built for compliance and change-management reviews.
Upload ArcGIS Pro map files (.mapx), track versions, and publish directly to ArcGIS Server as map or feature services. Per-environment connection remapping rewrites database and service references automatically before the Service Definition is built.
Register all items from an ArcGIS Portal group or a configured environment user in a single action. Duplicates are skipped automatically and each new item receives an initial snapshot immediately after registration.
A swimlane timeline for every item and map file shows when versions were captured and which environments they were deployed to. Bezier curves connect each snapshot to its deployments so you can see the full promotion history at a glance.
Keep multiple Qonda Deploy instances in sync across isolated or air-gapped networks. Online mode syncs automatically between connected peers; offline mode exchanges a single bundle file across the network boundary - no persistent connection required.
Qonda Deploy installs as a Windows Service and connects to your ArcGIS environments using your existing credentials. No additional infrastructure required.
Register your ArcGIS environments - Online organisations, Portals for ArcGIS, or both - from the browser-based admin interface.
Add portal items to the catalog and capture their current state as a version. Each snapshot records the author, timestamp, and full item configuration.
Choose a version, pick a target environment, and trigger the deployment. If the environment requires approval, approvers are notified automatically.
Monitor live progress on the dashboard. Review the full deployment history and compare any two item versions with a detailed JSON diff.
Nothing else required
Qonda Deploy supports unlimited source and target environments across all Esri platform types with no additional configuration required per environment.
Full support for ArcGIS Online organisations as source or target environments for item promotion.
Works with ArcGIS Enterprise 10.5 and later. Supports built-in, Windows, token, and OAuth authentication.
Promote items from ArcGIS Online to Enterprise, or between Enterprise environments at different versions.
Register as many environments as you manage - DEV, TEST, STAGING, PROD, and everything in between - all visible from a single interface.
Support for environments with no direct network path between them. Two Qonda Deploy instances can sync online when connected, or exchange a single bundle file across the boundary when they are not.
Every deployment follows a traceable, audited path. Qonda Deploy sequences item promotions through your environments with approval gates where you need them.
Qonda Deploy runs entirely within your own infrastructure. Your ArcGIS credentials and content never leave your control.
Built by the team behind Qonda Reports, trusted by GIS teams worldwide for almost a decade.
Runs entirely within your own infrastructure. You choose where it runs and who can reach it - no shared tenancy, no external dependencies.
Your ArcGIS credentials, item configurations, and deployment history are never sent to Ope Ltd or any third party. All data remains on the server you control.
Manage operator access independently of ArcGIS portal admin accounts. Operators deploy without ever needing direct portal credentials.
HTTPS only with a self-signed certificate generated on install. Every response includes Content Security Policy and X-Frame-Options headers.
No outbound connections you don’t know about - even for licensing. What happens on your server stays on your server.
Qonda Deploy is purpose-built for GIS administrators and release managers. Here’s how it stacks up against the alternatives.
Exporting items from one portal and re-importing them into another by hand using the ArcGIS web interface.
The catch
Custom Python scripts using the ArcGIS API for Python to automate item promotion between environments.
The catch
Everything you need to know before getting started.
ArcGIS portal items are live objects stored in a portal database - not files on a filesystem. Git versions files; it has no concept of a web map, a feature service, or a hosted layer, and no way to read from or write to a portal.
Even if you exported portal items to JSON and committed them, you would still need custom code to:
Qonda Deploy does all of this natively. It captures items via the ArcGIS sharing REST API, translates environment-specific references at deploy time using its mapping engine, and applies changes through the portal's own methods. Git is the right tool for code - Qonda Deploy is the right tool for ArcGIS content.
Yes, fully. ArcGIS Online organisations are supported as source or target environments alongside Portal for ArcGIS. You can promote items from ArcGIS Online to an on-premise Enterprise portal, between two ArcGIS Online organisations, or in any combination of Online and Enterprise environments.
No. Each environment is configured with a single service account that Qonda Deploy uses to perform portal operations. Operators log in to Qonda Deploy only - they never see or need portal credentials, and they do not require direct portal access. Access levels within Qonda Deploy (viewer, deployer, admin) are managed independently of ArcGIS.
Qonda Deploy supports a range of portal item types out of the box, including:
Every version snapshot is stored in the Qonda Deploy catalog and is never modified or deleted by a subsequent deployment. If a deployment fails, the previous version remains intact and can be re-deployed to the same target with a single click. The dashboard shows failed deployments immediately with a full error message so the issue can be diagnosed and corrected before retrying.
Yes. Two Qonda Deploy instances can stay synchronised even when there is no persistent network path between them. When connectivity exists, sync happens automatically. When environments are separated by a network boundary - such as a classified network or physical air gap - a single self-contained bundle file is exported from one side, transferred across the boundary by whatever means is available, and imported on the other. No persistent connection is required at any point.
We offer a fully guided live demo and can arrange an evaluation deployment on your own infrastructure. Get in touch and we will set something up around your schedule.
One licence covers your entire deployment - no per-user or per-environment fees.
Self-hosted on your own Windows server. Full control over data and infrastructure.
Hosted and managed by Ope Ltd. No server to maintain, always on the latest version.
Get in touch to arrange a demo or ask us anything about Qonda Deploy and how it fits your ArcGIS environment.
Have a question or want to arrange a demo? Fill in the form below and we’ll get back to you shortly.