DevHubfor Creatio
clio · git · gh — one window

Ship Creatio work without living in the terminal.

A native desktop workbench for Creatio developers: environments, source-controlled workspaces, package & app deployment, SQL, and GitHub — all driven from one app.

Download for Windows
v0.9.2 · Windows 10/11 (x64) signed installer & auto-updates
—
installer downloads
v0.9.2
latest version
29
releases shipped
Counts update live from GitHub Releases.
What it does

Everything clio can do, with a real interface.

DevHub drives the tools you already have — clio, Git and the GitHub CLI — and turns every long operation into a streamed, cancellable job.

Environments

Register Creatio environments, ping them, set a default, install cliogate. Credentials stay in clio — DevHub never stores them.

Workspaces & Git

Create workspaces, add packages, review colorized diffs, commit and inspect history — GitHub Desktop, for Creatio packages.

GitHub, both ways

Sign in from Settings — browser or token — then create a repo straight from a workspace, pick one from a dropdown, or deploy back from a repo to restore a broken environment.

Deploy env → env

Move a package or a whole application between environments, with a drift guard that blocks pushing over changes you haven't pulled.

Data migration

Compare and copy lookup values — or any object's rows, with its foreign-key hierarchy mapped out — between environments, with an automatic rollback script.

SQL & export

Run SQL against any registered environment, read the results in a grid, and export the full set to CSV or Excel — no separate database client.

Jobs you can watch

Streamed logs, a live activity indicator, safe cancellation of process trees, and a job history that survives restarts.

Signed auto-updates

Releases are cryptographically verified against the project key. DevHub checks, downloads, verifies and installs itself.

The loop

Pull, commit, publish, deploy.

01

Pull

Bring editable packages from an environment into a local workspace.

02

Commit

Review the diff and commit to Git — history you can trust.

03

Publish

Create the GitHub repo from DevHub and push, private by default.

04

Deploy

Install to the next environment, with a backup and drift check.

Changelog

What's new

DevHub ships often — and updates install themselves after the first download.

v0.9.2latest
July 2026

Migration › Objects: honest about multi-package objects

An object like Account is defined and extended across many packages — nine, in a typical instance. The list now shows each object once but tells the truth about that: the badge reads its home package plus a count (e.g. CrtCoreBase +8), and hovering it lists every package the object touches. Objects that live in a single package just show that package, as before.

v0.9.1
July 2026

Migration › Objects: each object listed once

The Migration screen's Objects search used to list a common object like Account many times over — once for every package that defines or extends it. Because those entries shared a name, the list rendered scrambled and picking one object highlighted almost all of them. Now each object appears exactly once, so the list is clean and selection behaves.

v0.9.0
July 2026

GitHub sign-in without the scavenger hunt

Signing in to GitHub used to bury the one-time code in the Jobs log; now it appears right in Settings, with buttons to copy it and open the GitHub device page. Prefer not to use the browser flow at all? Paste a personal access token instead — it goes straight to the GitHub CLI over a private channel, and DevHub never stores or logs it. Workspaces also gain a repository picker: choose any repo from your GitHub account in a dropdown to set — or change — where a workspace pushes, instead of hunting down and pasting a remote URL. The manual URL box remains for repos outside your account.

v0.8.9 – v0.8.10
July 2026

Copy any object's data — and no more frozen window

The Migration screen now goes beyond lookups. A new Objects tab searches every entity in an environment — Lead, Contact, your custom objects — shows its columns and foreign-key hierarchy, and copies a chosen object's rows into another environment, with a rollback script written first. Alongside it, an important fix: running SQL against an environment other than your default used to freeze the whole window while the connection was established — Windows would even mark DevHub “Not Responding”. Those reads (SQL, packages, applications, lookups, objects and GitHub lists) now run off the interface thread, so the app stays responsive and only the screen you asked shows its loading state.

v0.8.8
July 2026

Every failure, collected in one place

A new app-wide Errors view gathers failures from every screen as they happen, with a toast when something new lands — no more losing an error message because you switched tabs. The SQL screen is reorganized into Editor, Saved queries and Errors tabs, and a failed query can be reloaded into the editor straight from its error entry.

v0.8.5 – v0.8.7
July 2026

DevHub comes to the Mac

DevHub now ships a universal macOS build (Apple Silicon and Intel) alongside Windows, with the same signed auto-updates. It finds your clio environments where the Mac build of clio actually keeps them, and job cancellation cleans up the whole process tree. Builds aren’t yet Apple-notarized, so the first launch is right-click → Open. One honest retirement: the marketing-content migration introduced in v0.8.3–v0.8.4 proved to fight the platform on real environments — dense per-environment references meant raw-SQL workarounds that bypassed Creatio’s own validation — and was removed in v0.8.7. The Migration screen instead focuses on what works reliably: lookups, and (since v0.8.9) any object’s data.

v0.8.4
July 2026

Move campaigns and emails between environments

The Migration screen now copies marketing content — campaigns, bulk emails, email designer templates, dynamic content, and campaign flow diagrams — from one environment to another with their original IDs, so everything that references them keeps working. Pick individual campaigns and bulk emails or move everything missing; parents a selected record needs come along automatically. References the target cannot satisfy are resolved for you: a missing contact or lookup is matched to the target's row of the same name where one exists, otherwise the field is cleared — and every such change is listed in the result. A rollback script is written before anything is inserted. If you installed v0.8.3, update: it shipped this feature without the reference resolution and fails on records owned by environment-specific contacts. Update, this feature was retired in v0.8.7 — see the note above.

v0.8.1 – v0.8.2
July 2026

Lookup capture fixed, sharper edges filed down

Capturing lookups no longer fails on environments where a lookup points at a table without a Name column, and values registered twice are no longer captured twice. The SQL screen now explains why RAISE NOTICE output comes back empty and how to get results into a grid, the Jobs screen keeps wide logs inside the page and can collapse the job list, and long filenames in the Workspaces change list stay readable.

v0.8.0
July 2026

Move reference data between environments

Package deployment moves your configuration between environments — but not the reference data sitting in lookup tables, unless it happens to be bound to a package. Two additions close that gap. Compare gains a Lookups tab that shows exactly which lookup values differ between two environments, down to the individual row. And a new Migration screen copies the lookups you pick from one environment to another — matched on each value's identity so the records that depend on them keep working, shown to you as SQL before anything runs, and backed by an automatic rollback script so the change can be undone.

v0.7.0
July 2026

Compare two environments, down to the schema

The new Compare screen answers the question that used to mean guesswork: is pre-prod still the same as dev, and what exactly differs. Capture each environment once, then see every differing package, system setting, feature and web service — and open a package to see which schemas moved, which is how duplicate-element collisions announce themselves before a deployment fails. Comparison runs against the saved snapshots, so re-comparing is instant and nothing is ever written to your environments. Setting values stay hidden unless you reveal them, and exported reports leave them out entirely, because that is where API keys live. The Packages screen also shows at last which packages are locked.

v0.6.0
July 2026

See what an application actually contains

Application tiles now show the developer, how many packages the app installs, the Creatio version it needs, and when it last changed — and you can filter by developer to separate your own apps from the stock ones. The new Details view opens the full descriptor: dates, links, the application's packages, and the pages it contributes.

v0.5.2
July 2026

SQL errors surface, packages filter by field

An important fix: when the database rejects a query, DevHub now shows you its actual error — clio reports those with a success code, so v0.5.1 could show a green tick instead. Update if you are on v0.5.1. The Packages screen also filters properly now: search by name or version, and pick a maintainer from its own list, with the two narrowing together.

v0.5.1
July 2026

Statements report success

Running an UPDATE or other statement in the SQL screen used to look like it had failed — DevHub showed clio's own success output as an error. It now says the statement ran successfully, and the export buttons step aside when there are no rows to write.

v0.5.0
July 2026

Updates that announce themselves

DevHub now tells you in the header when a new version is out — no need to go looking in Settings. It checks shortly after launch and every few hours, you can dismiss a release you're not ready for, and a check that fails while you're offline stays out of your way. Deployments are also more honest: when Creatio answers with a server error, the job is marked failed instead of green, even if the command line reported success.

v0.4.0
July 2026

A refreshed interface

DevHub's entire interface was rebuilt on a modern component system for a cleaner, more consistent look. It ships with matching light and dark themes that follow your Windows setting, and a new Appearance control in Settings to pin either one. Background environment health checks are quieter too — they no longer raise a burst of notifications when you open the app.

v0.3.2
July 2026

Clearer failure explanations

When a command fails, DevHub now explains the likely cause and the steps to fix it, with the raw technical detail tucked away but still available.

v0.3.1
July 2026

Finds your CLIs reliably

DevHub locates clio, Git, and the GitHub CLI from the live system PATH and the usual install locations, so a tool installed after your last sign-in is still found instead of showing as missing.

v0.3.0
July 2026

clio management, and a bigger SQL grid

DevHub now looks after the clio CLI it depends on: install it when it's missing, update it when a newer build ships, and repair a damaged install. Known failures are explained rather than dumped — a locked tool store now tells you a clio command is still running. The SQL grid also shows up to 5,000 rows (exports were always uncapped).

v0.2.9
July 2026

Saved SQL queries

Name and save queries locally, reopen them for editing, or rerun them against the environment they were saved for.

v0.2.8
July 2026

Clearer deployment outcomes

Failed deployments now explain what actually happened, so a red job is diagnosable at a glance.

v0.2.7
July 2026

SQL runner with CSV & Excel export

Run SQL against a registered environment from inside DevHub, read the result in a grid, and export the full result set to CSV or Excel.

v0.2.6
July 2026

Deploy from GitHub

Clone a repository at a chosen branch and install it straight into an environment — restore a broken environment from known-good source, or move a package onto a fresh one.

v0.2.5
July 2026

Live job indicator & auto-captured catalog

An activity indicator shows running jobs from any screen. Package and application lists are captured into the cache automatically on launch and when you switch environments.

v0.2.4
July 2026

Empty-first workspaces & GitHub from the app

Start an empty workspace and add only the packages you want, then create a private GitHub repo and push — without leaving DevHub.

v0.2.3
July 2026

New look & persistent job history

Refreshed branding, plus a job history that survives restarts so you can revisit past runs and their logs.

v0.2.1
July 2026

First public release

Signed Windows installers (NSIS & MSI) published to GitHub, with cryptographically verified auto-updates.

Requirements

  • Windows 10 or 11 (x64) — a small, signed native installer.
  • macOS 12 or newer — a universal build for Apple Silicon and Intel. First launch: right-click → Open (not yet notarized).
  • The clio CLI, Git and the GitHub CLI installed — DevHub drives them.
  • A registered Creatio environment, cloud or on-site, to connect to.

Built for trust

  • No credentials stored. clio owns your environment secrets — DevHub never holds them.
  • Every mutation is a job. Streamed output, serialized per environment, safe to cancel.
  • Signed updates. Verified against the project key before anything installs.
Feedback

Found a bug? Want something added?

DevHub is built by one developer, and every report shapes what gets fixed next. Requests and bug reports both go through GitHub issues — you'll need a free GitHub account, and you can follow the thread until it ships.

Report a bug

Something broke, failed silently, or told you the wrong thing. Include the DevHub version, what you did, and the job log if there is one.

Report a bug

Request a feature

A clio command you want a button for, a screen that should show more, a workflow that still sends you back to the terminal.

Request a feature

See what's already open

Check whether your problem is already known, add what you're seeing to an existing thread, or watch what's coming next.

Browse issues

Get DevHub

It reuses the clio, Git and GitHub tools you already have.

Windows

Download installer (.exe) Get the .msi
v0.9.2 · NSIS & MSI · signed · auto-updates after install

macOS Apple Silicon & Intel

Universal .dmg on the latest release. First launch: right-click → Open.
All releases