Skip to main content

High-Level Flow

  1. SDK calls POST /v0/jobs.
  2. API validates auth and workload guardrails.
  3. Job is persisted and queued.
  4. Fleet controller scales workers on demand.
  5. Worker executes simulation and uploads artifacts.
  6. Billing settles to Hardlight ledger.
  7. Customer downloads artifacts via presigned URLs.

Components

  • API control plane
  • Worker runtime
  • Runtime store (Postgres in production)
  • Queue (SQS in production)
  • Artifact storage (S3)
  • Autoscaling worker fleet (ASG)
  • Billing ledger integration

Scaling Behavior

  • 10k submitted jobs does not mean 10k EC2 instances.
  • Capacity follows queue depth and active workload.
  • Workers scale up/down automatically based on demand.