Manage Vertra Cloud from VS Code

​

What is it

The Vertra Cloud extension manages your applications, databases and workspaces from the editor: deploy, watch logs in real time, check metrics, edit environment variables, browse remote files and inspect application state, without opening the dashboard.

​

Installation

• Visual Studio Code — install “Vertra Cloud” from the Visual Studio Marketplace, or from the command line:
  code --install-extension VertraCloud.vertra-cloud
  
• Cursor — install “Vertra Cloud” from Open VSX, inside Cursor’s own extension search.
• Other editors that don’t index Open VSX or the Marketplace, such as Antigravity — download the .vsix file from a release and install it manually:
  code --install-extension vertra-cloud-<version>.vsix
  
  Replace code with the equivalent CLI command of your editor if it isn’t VS Code itself.

​

Connecting your account

Open the Vertra Cloud panel in the Activity Bar and choose one of two ways to connect:

• Connect account — opens your browser to sign in and authorize the extension. The session is stored using your editor’s secret storage; it never touches settings, workspace files or logs.
• Use API key — for environments without a browser. Create a key on the API keys page of the dashboard, scoped to what you plan to use from the extension (at minimum account:read and apps:read; add apps:write, apps:files, databases:read/databases:write, snapshots:read/snapshots:write, images:read/images:write or workspaces:read/workspaces:write as needed). Paste the key when prompted.

To revoke access, delete the key or session from the API keys page in the dashboard. Disconnecting in the editor only removes the local credential; it does not revoke the key on the server.

​

Linking a folder and vertracloud.config

Link a workspace folder to an application with Link current folder. The link is written to a vertracloud.config file at the folder root, the same format read by the CLI: The extension recognizes this file by name and gives it completion for known fields, hover descriptions, and inline validation for missing or malformed values. If you decline writing the file when linking, the extension keeps the link only for the current editor window.

​

Deploying

Deploy current project zips the linked folder and uploads it. What gets sent:

• Everything in the folder except entries matched by .vertraignore (or .vertracloudignore), with sensible defaults excluding version control folders, dependency folders and build output.
• A hard limit of 100 MB per upload; the extension fails before uploading if the folder exceeds it.

Deploying works on every plan, for new and existing applications, within the limits of your current plan. An option to restart the application as part of the deploy is offered after upload. Each deploy also asks for an optional message, filled in with the subject of the folder’s last git commit; it is what the version shows in the Rollbacks history.

​

Rollbacks

Rollbacks… on an application lists its versions, newest first, with status, author and date. Pick one to:

• Roll back to this version. If that version’s environment variables differ from the current ones, the extension lists the names that would change (never the values) and asks whether to restore them. The application restarts on the chosen code.
• View crash log of a version that stopped right after its deploy.
• Copy version ID.

Rolling back is available on every plan. See Rollbacks and zero-downtime deploys for what a rollback restores and how long each version is kept.

​

Logs and real-time output

Show logs prints recent output for an application in an Output channel. Toggle realtime logs opens a live stream in an Output channel, with automatic reconnection while it stays healthy; it stops for good if you turn it off, close the output channel, or the connection is rejected by the server. Logs are not shown in an integrated terminal.

​

Metrics

Show metrics summarizes CPU, memory and network usage for common time ranges directly in the editor, without a webview.

​

Web Analytics

Analytics… on an application asks which view you want and shows it as a text document in the editor: Summary, Performance, Errors or Requests, for common periods. Performance and Requests need a plan that includes them; see History and plans. It reads with the apps:read scope.

​

Environment variables

Manage environment variables lists variable names, and adds, edits and removes them. Values are masked by default; the extension never copies or logs a value without an explicit action from you.

​

Snapshots

Manage snapshots lists, creates, downloads and restores snapshots for applications and databases. Restoring always asks for confirmation. Manual application snapshots are available on every plan, with a daily limit per account.

​

Remote files

Open remote files mounts the application’s file system as a folder in the editor, under a vertra:// scheme. You can open, edit and save text files remotely; binary files open read-only. Deleting, moving or uploading files asks for confirmation first. This is only available on plans that include the file manager.

​

Databases

Create databases and control their lifecycle (start, stop, restart), view metrics, download the TLS certificate and reset the password. The password is shown once, right after a reset, and is never stored or displayed again afterward — if you lose it, reset it again. Browsing the contents of a database from inside it is not available through an API key and is not part of this extension; use the dashboard’s data explorer for that.

​

Docker images

The Docker Images view lists your custom Docker images with the status of the latest build (building, ready or failed), the reason when a build failed and the applications that run from each one. The images of a workspace appear under that workspace. Custom images are available on Pro, Business and Enterprise plans; on Starter plans the view is empty and creating an image tells you why.

• Create Docker image takes a folder or a GitHub repository; the branch is optional (leave it empty to use the repository’s default branch). A folder needs a file named exactly Dockerfile at its root. It is zipped as the CLI does: .dockerignore is respected, .env* files and symbolic links are never sent, and the extension stops before uploading a context over 100 MB (or over 512 MB uncompressed or 50,000 files).
• The Dockerfile is checked before the build starts. Refusals are listed with their line and block the build; warnings ask you to confirm.
• Rename Docker image and Edit Docker image description (right-click an image) change the name and the description without building anything; your applications keep running.
• Rebuild from folder replaces the whole build context. A rebuild never restarts your applications, and a failed build keeps the current version.
• Show build log replays the log of the build in an Output channel and follows it live while the build runs.
• List versions, Download build context, Link to GitHub and Unlink from GitHub (a push to the linked branch rebuilds the image).
• Delete image asks you to type its name and also deletes every application created from it. With an API key, deleting an image that has applications needs the apps:delete scope too.
• Create application from image asks for the name, RAM, whether it serves web traffic, the subdomain, the port (pre-filled with the first EXPOSE of your Dockerfile, or 80) and the variables.

For an application that runs from an image, Deploy is a commit: your files go on top of the image’s current build context and the image is rebuilt. The extension tells you how many applications use the image before sending; only the application you deployed restarts, and only if you ask for a restart. Publish to web asks for the port when the application was created without web, restoring a snapshot can also bring back the image version it was taken on (when that version still exists), and language, version, main file, start and build commands are not offered because they come from the image.

​

Workspaces

The extension lists workspaces you belong to and lets you browse and link their applications and databases according to your role’s permissions. Creating a workspace, sending invitations and managing members happen in the dashboard, not in the extension.

​

Folders and favorites

The extension’s folders and favorites are persisted on the account, not in the editor’s local storage. The extension lets you create, rename, recolor and delete folders and organize applications and databases inside them, as well as favorite and unfavorite resources. State is individual per scope: personal organization is different from the same resource’s organization in each workspace. Changes made through the extension generate activities in the history, just like the equivalent actions in the dashboard and in workflows. The extension’s folders aren’t Flow groups. Groups continue organizing elements on Flow’s local canvas; there’s no sync, migration, or shared state between the two.

​

Network

For applications on a plan that allows publishing, you can publish or unpublish, open the public domain, set a custom subdomain (where your plan allows choosing one), add, edit or remove custom domains (as many as your plan allows), view the DNS records to configure, and purge the edge cache.

​

Feature availability by plan

Exact limits and prices change over time; the dashboard and this documentation always show the current numbers for your account. See Plans and limits for details.

​

Privacy and Workspace Trust

• The session token or API key is stored only in your editor’s built-in secret storage.
• The extension does not collect telemetry and does not phone home.
• It only talks to api.vertracloud.app, plus your browser for the account authorization step; no request goes to any other host.
• In an untrusted workspace, deploying, uploading and writing to remote files are disabled; reading remote data may still work.

​

Main commands

​

Troubleshooting