JumpStart Deployment

JumpStart SAP Intelligence is deployed as a containerized Next.js application with a companion worker process and a PostgreSQL database. It can run near Cosmos in EY-managed infrastructure, in a client-dedicated stack, or split so JumpStart stays inside the client network while Cosmos remains EY-hosted.

Current Deployment Notes

• Deployment config drives KROKI_URL from environment variables with a public default.
• Document-generation guardrails, BBP document continuation, and DMS/output progress reporting are part of the runtime reliability boundary.
• Project members, groups, and journey grants live in native Cosmos project RBAC, so a deployment needs no separate access-sync job. Project member search is paginated and scoped to the authenticated project/user boundary.
• The same image runs the webserver and the worker; MODE selects which one starts.

Deployment Patterns

Runtime Components

Infrastructure Requirements

Required Environment

In deployed environments each COSMOS_*_SERVICE_URL points at that service's own host, for example https://<adk-host>. See Base URLs.

Keep secrets in KeyVault, Secret Manager, or Kubernetes secrets. Do not bake them into images.

Local Run

JumpStart runs on port 3001 locally. Start the webserver and worker separately:

cd jumpstart-sap-intelligence
NODE_TLS_REJECT_UNAUTHORIZED=0 npm run dev
NODE_TLS_REJECT_UNAUTHORIZED=0 npm run dev:worker

Run Prisma migrations before starting a fresh database. Default journeys, blueprints, and engagement templates are seeded by the app itself (ensureSeeded() in lib/data/seed); no prisma db seed step is configured.

npx prisma migrate deploy

Image And Helm

The Docker build uses Node.js 24 and runs on a distroless Node.js 24 image. It installs @cosmos/sdk from the private SDK repository and Motif packages from the Motif npm registry, so both credentials are build arguments.

docker build \
  --build-arg GITHUB_ACCESS_TOKEN=<github-token> \
  --build-arg MOTIF_NPMRC=<motif-registry-token> \
  -f deployment/docker/webserver/Dockerfile \
  -t jumpstart-sap:latest .

The container listens on port 3000. MODE=webserver (default) starts the Next.js server; MODE=worker starts the job worker from the same image.

Deploy with the service Helmfile values for the target cloud/environment. The webserver and worker need the same Cosmos, database, OAuth, and encryption configuration.

Onboarding Checklist

1. Create or select the Cosmos organization and record the org_id.
2. Create the Cosmos OAuth2 application for JumpStart and configure redirect URIs.
3. Configure JumpStart environment variables and secrets.
4. Run Prisma migrations; default journeys and templates are seeded on startup.
5. Add project members and groups, and review journey access in Settings → Project Access.
6. Configure LLM access through Cosmos org settings/BYOT.
7. Upload project documents to DMS and index KB collections if needed.
8. Add SAP, Oracle, or BTP connections in JumpStart and verify health checks.
9. Start the worker and submit a test durable chat job.
10. Check Observer for standard/eval traces after the test run.

Verification

Troubleshooting

Related Documentation

• Overview
• Architecture
• Integration Guide
• Cosmos Architecture