Not a locked-down panel. A real shell and a real CLI on every plan.
Everything the CLI does, the REST API does too. Grab a token, wire it into your own tooling and CI, and drive sites from anywhere.
Install InstaCLI, connect your SSH keys, pick a PHP and WordPress version per site, and script the whole flow with copy-pasteable examples.
Read the docsToken-authenticated endpoints to create, configure and delete sites. Drop them into your dashboards, onboarding flows and CI pipelines.
View the API referencePrefer the terminal? instawp login, then instawp create --name my-site --json
No ticket for a shell, no add-on for the API. The whole toolkit ships the second the site does, on the $2 sandbox the same as on production.
Full shell and file access on every site you own. Bring your own keys, drop in from the browser terminal or your own client, and run whatever you'd run on a box you rented. No top tier to unlock it.
The new InstaCLI pipes WP-CLI over HTTPS, so wp <site> … --api works behind firewalls and in CI where SSH never reaches. WP-CLI is also preinstalled on every site, and everything speaks --json for piping straight into your scripts.
Flip on Local Mount and your site's files appear as a drive over WebDAV. Mount it in Finder, a mapped drive or rclone, open the folder in VS Code (or Sublime, PhpStorm, whatever you live in), and edit the live files with your real tooling. No FTP upload dance.
Two ways in. An in-site WordPress MCP with 40+ structured tools, posts, plugins, themes, media, the database, files and logs, that any client like Claude Code or Cursor can drive. And InstaCode: a browser AI code IDE plus a published VS Code extension, so you build against the real site from the editor you already use. See AI & MCP →
Pick PHP 8.0 to 8.3 and your WordPress version per site, switch any time, and tune the memory limit, all without opening a ticket. Mirror a client's exact stack on a $2 sandbox before you touch their live box.
Connect a GitHub, GitLab or Bitbucket repo to any site and every push deploys on its own. Run composer and npm build steps after each deploy, and spin up a throwaway preview site for every pull request. No FTP, no manual upload.
Spin up or clone a site locally with instawp local create, WASM PHP and SQLite under the hood. No Docker to babysit.
Snapshot before a risky change with instawp versions create, restore in one command if it goes sideways.
One click or one command straight into wp-admin, no password copy-paste, no juggling client credentials.
Run queries against any site with instawp sql, no SSH tunnel, no exposing the database port.
Stream PHP and Nginx logs live with instawp logs --php --nginx -f while you reproduce the bug.
Switch between client teams with instawp teams switch and keep sites, tokens and billing cleanly separated.
Most hosts gate shell and API behind their top tier. Here the cheapest sandbox and production are the same machine, so what you build on a $2 box behaves exactly like the live site, and promoting it is one plan change with no migration.
The shell, the CLI, the API and the AI tooling, on the $2 sandbox the same as on the live box.
Every site you spin up plugs into the rest of the platform. Keep exploring:
Clone, test, push live
SSH, CLI, Git deploy, MCP
Provision sites by API
Save sites & reusable presets
Managed WordPress, per site
Buy, connect, or resell
Bring sites in, free
Connect your stack
Every site, one dashboard
Resell hosting, your brand
Panel for your clients
Sell ready-made sites
SSH, the CLI, WP-CLI and an MCP on a $2 sandbox you can promote with one plan change.