The Ambient Code Platform is an OpenShift-native platform that deploys a backend API, frontend, and operator into a managed namespace.
- OpenShift cluster with admin access
- Container registry access or use default images from quay.io/ambient_code
ocCLI configured
-
Deploy (from project root):
# Prepare env once cp components/manifests/env.example components/manifests/.env # Edit .env and set ANTHROPIC_API_KEY make deploy
This deploys to the
ambient-codenamespace using default images from quay.io/ambient_code. -
Verify deployment:
oc get pods -n ambient-code oc get services -n ambient-code
-
Access the UI:
# Get the route URL oc get route frontend-route -n ambient-code # Or use port forwarding as fallback kubectl port-forward svc/frontend-service 3000:3000 -n ambient-code
To deploy to a different namespace:
make deploy NAMESPACE=my-namespaceTo build and use your own images:
# Set your container registry
export REGISTRY="quay.io/your-username"
# Login to your container registry
docker login $REGISTRY
# Build and push all images
make build-all REGISTRY=$REGISTRY
make push-all REGISTRY=$REGISTRY
# Deploy with custom images
make deploy CONTAINER_REGISTRY=$REGISTRYCreate and edit environment file for detailed customization:
cd components/manifests
cp env.example .env
# Edit .env to set CONTAINER_REGISTRY, IMAGE_TAG, Git settings, etc.After deployment, configure runner secrets through Settings → Runner Secrets in the UI. At minimum, provide ANTHROPIC_API_KEY.
For cluster login and authentication, see OpenShift OAuth Setup. The deploy script also supports a secrets subcommand if you only need to (re)configure OAuth secrets:
cd components/manifests
./deploy.sh secrets# Uninstall resources
make clean # alias to ./components/manifests/deploy.sh clean