Overview of POC Factory

POC Factory turns requirements, proposals, and RFPs into AI and Physical AI proofs of concept. This documentation covers the v1.1.0 container release: choosing a deployment path, configuring the service, generating a first POC, and operating it.

The application provides a React web interface backed by FastAPI and NVIDIA NeMo Agent Toolkit workflows. Operators deploy the backend, frontend, and optional GitHub MCP proxy as a coordinated release set. Users work in the browser and do not need a source checkout or local Python installation.

Skip Ahead

• Choose a deployment path — Compare Docker Compose and Kubernetes before installing.

• Deploy with Docker Compose — Run the published NGC release bundle on one host.

• Deploy on Kubernetes — Configure the Helm chart for a shared service.

• Configure and validate — Check inference, security, storage, and a complete workflow.

• Use POC Factory — Navigate workflows, review generation, and work with completed POCs.

• Generate your first POC — Follow the browser workflow.

• Operate and restore — Check service health and protect durable state.

• Troubleshooting — Diagnose common deployment and generation symptoms.

Use Cases

• Generate an AI agent POC from a natural-language requirement or proposal, with generated code, tests, documentation, and a downloadable package.

• Review a generation before code is produced by enabling Human-in-the-Loop approval for the PRD, blueprint selection, and architecture.

• Accelerate a completed POC through deployment, evaluation, profiling, optimization, monitoring, and scaling workflows.

• Prepare model customization with synthetic data and a configured NeMo Microservices environment.

Core Concepts

• Release image set: The backend, frontend, and GitHub MCP proxy use the same 1.1.0 image tag or approved immutable digests. See the deployment reference.

• Inference profile: Generation needs either a complete administrator profile or a user profile saved in Settings. Chat and embedding roles must both validate.

• Validation gates: A generation result records which checks passed and which were skipped. Kubernetes defaults do not prove that a generated container builds and runs.

• Durable state: PostgreSQL records, generated POCs, NAT job state, saved credentials, and optional fine-tuning artifacts must be backed up and restored together.

Core Components

Component	Purpose
Frontend	Browser UI for Dashboard, Create, Generate, Accelerate, Finetune, RFP, and Settings
Generator backend	FastAPI and NeMo Agent Toolkit workflows, APIs, validation, and packaging
GitHub MCP proxy	Optional source and blueprint intelligence
PostgreSQL	User and POC records for a shared deployment
Phoenix	Optional tracing and observability

For component ports and configuration priorities, see the deployment reference.