Autogen V2 Is Live

NodeOps

Autogen V2 introduces concrete upgrades over V1 across project ingestion, deployment management, scaling, security, and operational visibility.

While Autogen V1 focused on proving that applications could be deployed without custom CI/CD pipelines or DevOps setup, V2 expands that foundation with the tooling required to operate, iterate, and scale deployed applications.

Specifically, Autogen V2 adds:

Manual project uploads alongside repository-based deployments
First-class support for NodeOps GPT projects, including code access after transfer
Environment-based deployments with promotion and auto-promotion
Configurable compute resources (CPU, memory, replicas) per deployment
Built-in security scanning with scores, vulnerability reports, and re-scans
API key management for application integrations
A redesigned UI with clearer separation between CI/CD, environments, and deployments

The sections below walk through each of these additions and explain how they change the deployment experience in practice.

Manual Project Uploads

Autogen V2 now supports manual file upload project creation.

This means you can:

Upload project files directly
Build & deploy without connecting a repository
Iterate quickly on local or generated code

This is especially useful for quick experiments, prototypes, or projects generated via other tools.

NodeOps GPT Project Visibility

Projects deployed through NodeOps GPT are now first-class citizens in Autogen V2.

Once you transfer a GPT-built app:

The project appears inside Autogen V2
You can view the deployment details
You can download the generated code files

This closes the loop between “idea → chat → deployment → iteration,” giving builders full ownership and visibility over what they’ve created.

Environments and Deployment Promotion

Autogen V2 introduces dedicated environments.

Builders can now:

Create environments (for example: staging or production)
Promote deployments into environments
Enable auto-promote, which automatically links the latest deployment to an environment

This makes it easier to manage live versions of an app without manually tracking links or redeploying from scratch.

Compute Configuration and Scaling

Compute is no longer a black box.

Autogen V2 exposes compute resource information directly in the UI and allows real-time configuration changes.

You can now:

Vertically scale CPU cores and memory
Horizontally scale replicas
See the active configuration in the deployment overview

Scaling decisions become explicit and adjustable, without redeploying or reconfiguring pipelines.

Built-In Security Scans

Every deployment in Autogen V2 now includes a security scan.

Builders can:

View a security score per deployment
Inspect detected vulnerabilities
Fix issues and re-scan
Download a full PDF security report

This brings security feedback closer to the deployment flow, instead of treating it as a separate tool or afterthought.

API Keys for External Integration

Autogen V2 introduces API keys.

This allows builders to:

Generate API keys directly in Autogen under the Profile page
Configure integrations with external applications or workflows
Use Autogen as part of a broader toolchain

Playground and UI Improvements

The Sandbox has been renamed to Playground, reflecting its role as a space for experimentation.

Alongside this, Autogen V2 ships with a cleaner, more structured UI, with clearer separation across:

Projects
Environments
Deployments
CI/CD management

The goal is simple: reduce cognitive overhead as projects grow.

Migrating From Autogen V1

If you’ve already deployed projects on Autogen V1, migration to V2 is required.

The process is straightforward:

Migrate your projects from autogen.nodeops.network to autogen-v2.nodeops.network
The deployment flow remains unchanged
Autogen V1 will be sunset on January 15
If you run into any issues, reach out via our support channels and the team will assist promptly