Installation or instant launch
Before you work with the API, choose how you want to run Callaba Engine. Most teams start with one of two paths: an instant cloud launch for faster evaluation, or a self-hosted deployment for infrastructure control.
Launch on AWS
If you want the fastest start, use the AWS launch path. It is the right option when you want to bring up an instance quickly, validate the API, and begin testing flows without first preparing your own Linux host.
Install self-hosted or on-premises
If you need more control over networking, deployment topology, or where the system runs, use the self-hosted path. We currently keep two practical installation guides depending on the product version you need.
Which path should you choose?
- AWS launch is usually better when you want the shortest path to a running instance and immediate API testing.
- Self-hosted / on-premises is usually better when you need deployment control, internal network placement, or version-specific installation planning.
Once the instance is available, the next docs step is usually Authorization, where you copy the JWT token from the dashboard and send it as x-access-token.