Start here
5-minute quickstart
The shortest path to a real CALIBER success: bring up the local stack, verify readiness, or jump into the right next guide.
Use this page when you want the shortest path to a real CALIBER success before you decide which deeper guide you need.
At a glance
| Goal | Start here | Then go to |
|---|---|---|
| Run CALIBER locally | make setup, make start | Local bring-up |
| Verify a shared deployment | open the UI and check readiness | Choose your CALIBER path |
| Make the first Python call | SDK guide | Auth and project scoping |
| Tour the product before integrating | Guided walkthrough | Trust and governance |
1. If you have a local checkout
Bring up the default local stack:
make setup
make startThen verify:
- CALIBER UI loads at
http://127.0.0.1:5001/caliber/ - the readiness surface responds
- you can log in and reach the product shell
Use Local bring-up if you need the operator path instead of the shortest happy-path summary.
2. If CALIBER is already running somewhere
Do not start with architecture. Start by answering one practical question: what are you here to do?
Use one of these next pages:
3. Verify that the system is usable
For operators, the meaningful check is readiness rather than simple process health.
Use:
4. Pick the right next track
| If you are... | Read this next |
|---|---|
| Integrating from Python | SDK guide |
| Working at the raw HTTP layer | REST API overview |
| Operating the stack | Configuration and provider setup |
| Using CALIBER features | Prompts, Workflows, Knowledge bases |
| Reviewing trust and release posture | Trust and governance |