oblako simulates the topology around real local engines. Real behavior, not a mock.

Documentation

oblako

oblako is a local AWS platform: run Bedrock, SageMaker, Redshift, Step Functions and more on your laptop, no cloud required. You write the AWS code you already write, every service maps 1:1 to a boto3 client, and oblako runs it against real local engines wired into an AWS-shaped topology.

import boto3

s3 = boto3.client("s3")          # -> S3Proxy, real S3 API over the filesystem
s3.create_bucket(Bucket="demo")

ddb = boto3.client("dynamodb")   # -> DynamoDB Local
ddb.list_tables()

The difference from a mock: a bucket really stores bytes, a redshift-connector session really runs SQL, a SageMaker job really trains in a container. oblako fakes the topology (clusters, endpoints, control planes) around engines that are genuinely doing the work, real behavior, simulated topology.

Services

Every service is the local counterpart of an AWS service, reached through its normal boto3 client (or native driver):

Full per-service guides, limitations, and the Python API are in the documentation.

Quick start

oblako needs Python 3.10 or later and a container runtime: Docker (the default), or Podman, Colima or Apple's container (see below). Most services run as containers; a few API engines run in Python without one.

pip install oblako         # or: uv tool install oblako

oblako up                  # start the services
oblako configure           # write the `oblako` AWS profile
export AWS_PROFILE=oblako  # point boto3 and the AWS CLI at oblako
oblako dashboard           # web UI at http://localhost:8000

Your unmodified boto3 code and the AWS CLI then reach the local services, with no endpoint_url in the code. Select another AWS profile and the same code talks to AWS.

CLI

Service names: bedrock, opensearch, redshift, rds, moto, s3, dynamodb, kinesis, stepfunctions, iceberg, trino (ollama aliases bedrock; aurora aliases rds).

Container runtimes

oblako isn't hard-wired to Docker, every service runs through a pluggable backend, selected with OBLAKO_CONTAINER_BACKEND: docker (default), podman, colima, kubernetes, or Apple's container (apple). See the runtimes guide.

Documentation

The full docs (architecture, every service with its limitations, the dashboard, container runtimes, and the Python API reference) live at oblako-sdk.almostly.ai.

License

oblako is open core. This repository is the open-source edition, licensed under the Apache License 2.0; see NOTICE. Commercial Pro and hosted editions are offered separately under their own terms.

oblako orchestrates third-party engines (moto, S3Proxy, Trino, Postgres, and others) that it pulls at runtime rather than redistributing; each keeps its own license. Two of them (Citus, DynamoDB Local) carry terms that matter for commercial use, inventoried in THIRD_PARTY_LICENSES.md.