---
title: Get Started - Run stdapi.ai locally or on AWS
description: Pick your path to try stdapi.ai - a one-line Docker run for local development,
  or a two-command Terraform deployment on AWS.
keywords: stdapi.ai getting started, try stdapi.ai, OpenAI gateway AWS, Anthropic
  gateway AWS, AWS Bedrock quickstart, Docker local AI gateway, Terraform AI gateway
---

# :material-rocket-launch: Get Started

Two ways to get an OpenAI-, Anthropic-, Cohere- and Ollama-compatible endpoint in front of Amazon Bedrock. Both give you the same API; pick by where you are today.

## :material-directions-fork: Pick Your Path

<div class="grid cards" markdown>

-   :material-aws:{ .lg .middle } __Two commands: deploy on AWS with Terraform__

    ---

    **Start here — recommended for production.**

    - 2 Terraform commands → ECS Fargate with HTTPS, auto-scaling, optional WAF
    - Hardened container image (`ghcr.io/stdapi-ai/stdapi.ai-community`), free under AGPL-3.0, with no subscription
    - IP-restricted by default — safe to test right away
    - Multi-region variants available (EU / US) for data residency

    [:octicons-arrow-right-24: Deploy on AWS](operations_getting_started.md){ .md-button .md-button--primary }

-   :material-docker:{ .lg .middle } __One command — Try locally with Docker__

    ---

    **Lighter option, for:** local development, evaluation, open-source projects.

    - One `docker run` command — no AWS infrastructure to provision
    - Uses your local AWS credentials (mounted from `~/.aws`) to reach Bedrock
    - No authentication or IP restriction by default — intended for local use only
    - Free hardened container image (AGPL-3.0)
    - Full API compatibility — same endpoints as production

    [:octicons-arrow-right-24: Run Locally with Docker](operations_getting_started_local.md){ .md-button }

</div>

Looking for reference documentation rather than a quickstart? See [Features](features.md) for what the gateway does, and the [API Overview](api_overview.md) for endpoints, parameters, and SDK usage.

<span id="before-you-start"></span>

??? info "Before you start"
    Both paths need:

    - **An AWS account** with access to [Amazon Bedrock](https://aws.amazon.com/bedrock/). [Create one free](https://aws.amazon.com/free/) if you don't have one.
    - **AWS credentials configured locally** — `aws configure` or `aws sso login` ([AWS CLI setup guide](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-quickstart.html)).

    The AWS Terraform path additionally needs:

    - **Administrator-level AWS permissions** — the module provisions IAM roles and policies, KMS keys, ECS/Fargate, ALB, and networking. A restricted developer profile will fail.
    - **A sandbox AWS account is strongly recommended** for evaluation. Replicate into your target account once you've validated the stack.
    - [Terraform](https://www.terraform.io/downloads) or [OpenTofu](https://opentofu.org/docs/intro/install/) >= 1.9.
    - Internet access from the tasks, to pull the image from GitHub Container Registry. Without it, mirror the image into your own Amazon ECR.

    The Docker path additionally needs [Docker](https://docs.docker.com/get-started/get-docker/) or [Podman](https://podman.io/docs/installation).

---

## :material-help-circle-outline: Not Sure Which to Pick?

| You are... | Go with | Why |
|---|---|---|
| A developer evaluating for the first time | **Docker (local)** | Fastest feedback loop, no cloud resources to tear down. |
| A team lead validating for production use | **AWS (Terraform)** | Mirrors real deployment. |
| Already running a production workload elsewhere | **AWS (Terraform)** | Jump straight to the stack you'll operate long-term. |
| Contributing to an open-source project | **Docker (local)** | AGPL-3.0 container image is free to use and redistribute. |

You can start local and migrate to AWS later — same API, same SDKs, same client-side changes. Point the base URL at your AWS endpoint, add that deployment's API key, and check your model names against what its regions serve.

---

## :material-connection: Pointing a Client at It

Both paths are adopted the same way: point your client at the deployment's base URL, give it that deployment's API key, and change the model name only where it differs. Usually it does not — each model is published under the name its provider uses, so a client already asking for `claude-opus-5` or `gpt-5.6-sol` changes nothing but the base URL. Where a name *does* differ, [`MODEL_ALIASES`](operations_configuration_models.md#model-aliases) maps the name your application already sends onto a model the deployment serves.

What the base URL buys is the catalogue behind it: it spans every provider your regions offer, not one vendor's list. [`GET /search_models`](api_search_models.md) lists it, and the [Models](models.md) page shows the same catalogue now, before you deploy.

---

## :material-arrow-right: After Your First Call

<div class="grid cards" markdown>

- :material-star-four-points-outline: [**Features**](features.md) — What the gateway supports, substantiated claim by claim
- :material-book-open-variant: [**API Overview**](api_overview.md) — Endpoints, parameters, and SDK usage
- :material-magnify: [**Search Models**](api_search_models.md) — Find the right model ID by modality, route, region, or streaming support
- :material-view-list: [**Models**](models.md) — Browse every model with modalities, regions, AWS prices and leaderboard scores
- :material-puzzle: [**Use Cases**](use_cases.md) — Open WebUI, n8n, coding assistants, and more
- :material-cog: [**Configuration**](operations_configuration.md) — Every environment variable and option
- :material-wrench: [**Troubleshooting**](operations_troubleshooting.md) — Common first-deployment errors and fixes
- :material-server-network: [**Advanced Deployment**](operations_deploy_advanced.md) — VPC integration, multi-region, cost optimization
- :material-scale-balance: [**Licensing**](operations_licensing.md) — AGPL-3.0-or-later terms

</div>
