Deploy, govern, and operate RightAPI Forge.

Quick start

Clone the public repository, create the environment file, and launch the signed application stack.

git clone https://github.com/shaike1/rightapi-forge
cd rightapi-forge
cp .env.example .env
docker compose up -d

Open the product site at port 19123, then enter the console through /app/.

Architecture

The control plane keeps identity, policy, approvals, execution, persistence, and evidence separate from model providers. Providers can change without moving the operational trust boundary.

• Express API and React operations console
• Tenant-aware RBAC and credential isolation
• Agents, runbooks, workflows, and bounded tool execution
• SQLite-backed operational stores and exportable release evidence

Operate

Begin with health checks and a backup policy before connecting production targets. Use approval gates for any action that can alter infrastructure or deploy generated code.

Security

Keep the console behind trusted identity, store secrets outside source control, restrict tool targets, and review audit evidence before promoting releases.

Reference

The running deployment exposes an OpenAPI explorer. The source repository contains the complete API, developer, integration, and multitenancy references.