Use this command to install Forgevena with WinGet:
winget install --id=RohitKumarNaidu.Forgevena -e
[Software Name] is a governed engineering tool designed to streamline development workflows from idea to production. It provides enterprise-grade project bootstrapping, AI provider governance, cloud preparation, and release engineering in one cohesive platform.
Key Features:
Enterprise Project Bootstrapping: Supports templates for React, Next.js, FastAPI, Express, Python, Flutter, AI agents, RAG, full-stack AI, microservices, libraries, CLI tools, and blank projects.
Safety-First Initialization: Uses preview-first initialization to protect existing files and directories, ensuring no accidental data loss or overwrites.
Governed AI Integrations: Manages OpenAI, Anthropic/Claude, Gemini, OpenRouter, and Ollama with explicit consent controls, secret-reference-only configuration, and streaming capabilities.
Cloud Preparation & Deployment: Validates and deploys to Render, Railway, Vercel, AWS, Azure, Google Cloud, and more with dry runs and rollback guidance.
Cross-Platform Support: Runs on Windows 11, WSL2/Linux, and macOS across x64 and arm64 architectures with Node.js 20.19 or newer.
Target Audience and Benefits:
Ideal for modern engineering teams seeking to accelerate development without compromising governance or security. Forgevena streamlines project setup, integrates AI responsibly, ensures cloud readiness, and automates release cycles while maintaining strict data integrity and privacy controls. Available via winget for seamless deployment in enterprise environments.
README
Forgevena
Governed engineering from idea to production.
Enterprise project bootstrap, governed AI providers, MCP and plugin controls, secure local state, cloud preparation, validation, upgrades, diagnostics, and automated release engineering through one safety-first CLI.
Modern engineering teams repeatedly solve the same setup, governance, integration, and release problems. Forgevena turns those practices into an additive and auditable developer platform without replacing application code or silently transmitting project data.
Release status:v1.3.0 remains the current stable installation. Repository metadata may identify v1.4.0-rc.1 while its provider-platform release candidate is validated; prerelease metadata is not a stable-support claim.
Features
Enterprise bootstrap: React, Next.js, FastAPI, Express, Python, Flutter, AI agent, RAG, full-stack AI, microservices, library, CLI, blank, and enterprise templates.
Existing-project safety: preview-first initialization that skips every existing file and protects application directories.
Release downloads include smoke-tested Windows, Linux, and macOS x64 executables, checksums, SBOMs, provenance, verification evidence, and package-manager bundles on the GitHub Releases page. Verify native files against RELEASE_SHA256SUMS; npm users can verify the stable version with npm view forgevena version.
Install from Homebrew
The maintained Forgevena Homebrew tap installs the verified native executable on Linux and Intel macOS:
brew install rohitkumarnaidu/forgevena/forgevena
forgevena version
forgevena doctor
The current tap supports x64 release assets. Use npm on arm64 until native arm64 assets are published. Winget 1.2.3 is published upstream; Chocolatey 1.2.3 has passed automated checks and remains in human moderation. See the installation guide for authoritative channel versions and status.
For an existing repository, always preview first:
cd ExistingProject
forgevena init --dry-run --verbose
forgevena init --apply
The legacy ai-workspace executable and .ai-workspace/ state directory remain supported throughout the 1.x release line. See the migration guide.
Safety Model
Project changes preview by default; local writes require --apply.
Existing files, manifests, and application directories are never overwritten.
External commands require an impact plan and explicit approval.
Tracked provider configuration stores environment-variable references, never secret values.
Prompts, responses, credentials, authorization headers, and MCP payloads are redacted from logs.
MCP servers and plugins remain disabled until explicitly trusted and activated.
Rollback removes only unchanged files recorded as managed assets.
flowchart LR
Idea["Idea"] --> Spec["Requirements and specification"]
Spec --> Preview["Forgevena dry run"]
Preview --> Approval["Human approval"]
Approval --> Apply["Additive apply"]
Apply --> Validate["Validation and tests"]
Validate --> Release["Governed release"]
Release --> Operate["Health and operations"]
Architecture
flowchart TB
CLI["Forgevena CLI"] --> Foundation["Foundation services"]
Foundation --> Bootstrap["Bootstrap and templates"]
Foundation --> Registry["Registry and managed assets"]
Foundation --> Integrations["Integrations and capabilities"]
Foundation --> Providers["Providers, credentials, MCP, plugins"]
Foundation --> Delivery["Docker, cloud, docs, and release"]
Bootstrap --> Project["Developer-selected project"]
Registry --> Project
Integrations --> Project
Providers --> Project
Delivery --> Project
The architecture is intentionally modular and frozen for the 1.x line. New core abstractions require demonstrated need and an approved ADR. Read the architecture guide and ADR index.
Forgevena was developed through an AI-assisted engineering workflow using Codex and GPT-5.6 for architecture planning, implementation, testing, documentation, CI/CD repair, security review, and release engineering. Changes were reviewed and validated with automated tests and GitHub Actions before release.
Project Preview
The repository includes placeholders for future verified screenshots and terminal demonstrations. Published media must redact credentials, personal paths, project data, and provider responses.
Roadmap
The stable platform prioritizes compatibility, validation, security hardening, account-backed integration verification, and community-requested improvements. See ROADMAP.md.
Do not report vulnerabilities publicly. Follow SECURITY.md and use GitHub private vulnerability reporting when available. General support channels and response expectations are documented in SUPPORT.md.
Contributing
Focused contributions are welcome. Every change must preserve additive safety, consent gates, secret isolation, backward compatibility, tests, and documentation. See CONTRIBUTING.md and GOVERNANCE.md.
