VS Code in the browser (code-server)
The real editor, running against your site's files: extensions, multi-file search, an integrated terminal and git built in. Open a site, make the change, commit it — no local checkout and nothing to install.
Site tools
VS Code in the browser, a jailed SSH shell, wp-cli, phpMyAdmin, a file manager, per-site cron and environment variables, and full control of PHP — all in the dashboard, all scoped to your site alone. This is a developer's control surface, not a settings page.
Most hosting control panels stop where the work starts. You can toggle a setting or two, then you are expected to open an FTP client, find a database tool, SSH in from somewhere else and stitch the job together yourself. Zinn Digital® puts the whole toolchain inside the site itself: open a site in the dashboard and the editor, terminal, database, files, cron, environment and logs are already there, already authenticated, already pointed at the right site.
Every one of those tools runs inside the site's own cage. CloudLinux CageFS gives each tenant an isolated filesystem view, so a shell, an editor or a file manager can only ever see that tenant's files — not other sites, not other customers, not sensitive system paths. The convenience of a shared panel with the separation of a private box.
The editing surface is a full IDE, not a textarea with syntax colouring.
The real editor, running against your site's files: extensions, multi-file search, an integrated terminal and git built in. Open a site, make the change, commit it — no local checkout and nothing to install.
wp-cli is available in the panel terminal and over SSH. Search-replace a domain, activate a plugin, flush rewrites, export a database, run a cron event on demand — the standard WordPress toolkit, in the same window as your code.
The dashboard AI assistant works alongside the editor on your own model keys, reading and editing files and running wp-cli for you. Bring your own model; the platform provides the hands.
Prefer your own tools? Connect over SSH, SFTP or FTP and get the same jailed view of the same files. Access keys and credentials are managed in the dashboard on a least-privilege basis, and privileged actions are audit-logged.
Per-site runtime configuration — not a server-wide setting you have to raise a ticket to change.
Choose the PHP version for each site independently using CloudLinux alt-PHP. Run a legacy plugin on an older branch while the site next door runs current — no shared runtime, no compromise version for the whole account.
memory_limit, max_execution_time, upload and post size and the rest are yours to set within your entitlement, so an import script or a large media upload does not need a support conversation.
Enable or disable PHP extensions per site — imagick and gd, redis and memcached, bcmath, intl, soap and more — so a site carries exactly the extensions it needs and nothing it does not.
Each site gets its own LiteSpeed LSAPI workers, with the count configurable within your tier and bounded by the site's LVE entry-process limit. Concurrency is yours; a neighbour's traffic spike is not your queue.
Redis or Memcached object caching per site, with the WordPress object-cache drop-in wired in — dynamic pages stay fast under load instead of hammering the database.
Manage WP-cron and real system cron per site, and set environment variables for the site's runtime — API keys, feature switches and stage flags — without editing wp-config by hand.
Direct access to the two things developers actually need to reach.
Both database tools are built into the dashboard and single-sign-on'd — click through from the site and you are already authenticated against the right database. No separate credentials to store or share.
Each site runs on MariaDB with as many databases and users as the project needs, plus a remote-access toggle when you want to connect an external client or reporting tool.
Per-site database usage is throttled by CloudLinux MySQL Governor, so one site's heavy queries cannot slow the server for everyone else — including yours.
A full file manager (FileGator), embedded and SSO'd, for uploads, permissions, archives and quick edits when opening the IDE is more ceremony than the job deserves.
Read the site's access, error and PHP logs from the dashboard while you work — the fastest route from 'it broke' to the line that broke it.
The tools know they are managing WordPress, so the common jobs are one action rather than ten.
Access to these tools follows your organisation's roles. Customer memberships carry an owner, billing, dev or read-only role, and permissions resolve from those roles — the dev role is a working developer's role, and deploying or pushing to live is deliberately not part of it. Staff access is equally bounded by its own department roles and permissions.
Programmatic access uses per-organisation API keys and OAuth clients with granular scopes — read-only, billing or provisioning — so an automation gets exactly the reach it needs. Every privileged action is audit-logged with actor, action and target, which means the answer to 'who changed the PHP version on Tuesday' is a lookup rather than an argument.
If you would rather drive all of this from an AI tool, the same capability is exposed through our hosted MCP server — run wp-cli, clone to staging, purge cache or restore a snapshot from Claude, Cursor or any MCP-capable agent, under the same role scoping and audit trail.
Mainstream hosting is full self-service: the complete tool set, exposed and editable within your plan's entitlements. Footprint-Free hosting is deliberately more standardised and locked down, because a network's whole value depends on its sites presenting a uniform, unremarkable surface — configuration freedom is a footprint of its own.
Entitlements do the rest of the gating. PHP workers, disk and extensions scale with your tier, so the shape of the tooling is the same on every plan while the headroom grows with it. If you are unsure which line fits, start on the card-free 7-day trial and look at the panel yourself before deciding.
Yes — it is code-server, VS Code running in the browser against your site's files. You get extensions, multi-file search, an integrated terminal and git, and it edits the site's filesystem directly from the dashboard. Optional AI assistance works inline using your own model keys.
You get a jailed shell over SSH, plus SFTP and FTP, with keys and credentials managed in the dashboard on a least-privilege basis. The jail is CloudLinux CageFS: each tenant gets an isolated filesystem view and cannot see other tenants, other sites or sensitive system files, which contains a breach rather than letting it spread. No isolation model makes compromise impossible, so real-time scanning, the proactive WAF and audit logging run alongside it.
Yes. PHP version is selected per site via CloudLinux alt-PHP, settings such as memory_limit, max_execution_time and upload size are editable within your entitlement, and extensions like imagick, gd, redis, memcached, bcmath, intl and soap are toggled per site. Your PHP worker count is configurable within your tier, bounded by the site's LVE entry-process limit.
phpMyAdmin and Adminer are embedded in the dashboard and single-sign-on'd, so you click through from the site and you are already connected. Each site runs MariaDB and can have multiple databases and users, with a remote-access toggle for external clients. MySQL Governor throttles per-site database usage so heavy queries on one site cannot slow the server.
Yes. Per-site cron management covers both WP-cron and real system cron, and environment variables are set per site for the site's runtime — so scheduled tasks and configuration live with the site rather than buried in a file you have to remember to migrate.
Mainstream hosting is full self-service with the complete tool set. Footprint-Free is intentionally more standardised and locked down, because per-site configuration variation is itself a footprint. Entitlements gate the rest — workers, disk and extensions — so what you can adjust scales with your tier.
Access follows organisation roles: owner, billing, dev and read-only for customers, with permissions resolved from those roles. The dev role does not include deploying or pushing to live. Programmatic access uses per-organisation API keys and OAuth clients with granular scopes, and every privileged action is audit-logged with actor, action and target.
Start a card-free 7-day trial, deploy a site and put the IDE, terminal, database tools and PHP controls through their paces. 30-day money-back guarantee, free migrations, no lock-in.
Start free