Environments
Register Creatio environments, ping them, set a default, install cliogate. Credentials stay in clio — DevHub never stores them.
A native desktop workbench for Creatio developers: environments, source-controlled workspaces, package & app deployment, SQL, and GitHub — all driven from one app.
DevHub drives the tools you already have — clio, Git and the GitHub CLI — and turns every long operation into a streamed, cancellable job.
Register Creatio environments, ping them, set a default, install cliogate. Credentials stay in clio — DevHub never stores them.
Create workspaces, add packages, review colorized diffs, commit and inspect history — GitHub Desktop, for Creatio packages.
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.
Move a package or a whole application between environments, with a drift guard that blocks pushing over changes you haven't pulled.
Compare and copy lookup values — or any object's rows, with its foreign-key hierarchy mapped out — between environments, with an automatic rollback script.
Render an entity-relationship diagram from any objects you pick — their columns and the real foreign keys between them — then pan, zoom, fit and export it as SVG or PNG. A second tab lists every schema's package dependencies and which package holds the latest version.
Watch a Creatio environment's own log as it happens — pick a level and a logger, filter while you read, pause without losing your place, and save what's on screen. Needs cliogate on the environment.
Read Creatio's feature toggles as they stand right now, switch them, and compare two environments side by side — the form the question usually takes: why does this work on dev and not on pre-prod?
Browse an environment's schemas in a package explorer, open several as tabs, and edit the source in a full code editor with Creatio-aware suggestions. See exactly what a change would do before it is saved.
Compile, flush Redis and restart as one tracked job, in the order that makes a failed compile stop before anything is torn down — the steps that get freshly installed code actually live.
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.
Streamed logs, a live activity indicator, safe cancellation of process trees, and a job history that survives restarts.
Releases are cryptographically verified against the project key. DevHub checks, downloads, verifies and installs itself.
Bring editable packages from an environment into a local workspace.
Review the diff and commit to Git — history you can trust.
Create the GitHub repo from DevHub and push, private by default.
Install to the next environment, with a backup and drift check.
DevHub ships often — and updates install themselves after the first download.
The Schemas screen is now a place to work rather than a viewer. Source opens in a full code editor — syntax colouring for JavaScript, C# and SQL, find and replace, undo, multi-cursor, and Ctrl+S to save. A package explorer replaces the flat list, several schemas stay open as tabs with their own edits, and Ctrl+P jumps straight to any schema by name. Suggestions understand Creatio: Freedom UI request names, handler and lookup-filter skeletons, ESQ and web-service snippets for C#, and real table names from your environment while writing SQL. Formatting is available for JavaScript and SQL.
Apply changes runs compile, flush Redis and restart as one job, in that order, so a failed compile stops before anything is torn down. A new Features screen reads Creatio's feature toggles as they stand, switches them, and compares two environments side by side. Schemas arrived: open a server schema's source, see exactly what an edit would change, and save it back — with a refusal rather than an overwrite if someone else changed it meanwhile. SQL and ping moved to a direct connection: ping answers in about a tenth of a second and now reports whether Creatio reached its database and loaded its configuration. Adding a package a workspace already has now offers to pull it.
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.
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 bugA 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 featureCheck whether your problem is already known, add what you're seeing to an existing thread, or watch what's coming next.
Browse issuesIt reuses the clio, Git and GitHub tools you already have.
.dmg, signed. First launch: right-click → Open.