Overview
Skippr Cloud gives your application a small set of managed capabilities with stable hostnames under cloud.skippr.io.
Motive: build without coarse AWS billing units or scaling levers. Cloud is intended for development environments and low-risk / mid-market production workloads.
Capabilities
| Capability | Job | Compat |
|---|---|---|
| gateway | HTTP API Gateway — Apis, routes, integrations; platform edge + your APIs | API Gateway–class |
| auth | People, API keys, workload identity, ABAC | Cognito / IAM–class |
| tables | Document / KV tables (PK/SK, GSI, conditionals) | DynamoDB JSON |
| objects | Buckets and objects | S3-shaped |
| streams | Append log (topics / partitions / consumer groups) | streams protocol |
| queue | Durable work queues | SQS JSON |
| events | Event bus, rules, targets | EventBridge–class |
| scheduler | Named schedules that fire into events or queue | EventBridge Scheduler–class |
| functions | Short-lived invoke | Lambda–class |
| machines | Long-lived VM fleets | ASG–class |
| elt | Extract-load APIs + runner / warehouse ELT | — |
AWS product names are compatibility aliases, not Skippr product brands.
Region
v1 region label: eu-central-1. Service hostnames follow {service}[.region].cloud.skippr.io (see Gateway).
Access model
- Obtain Cloud credentials (API key or SigV4 access keys) from auth.
- Call gateway (or the service hostname when published).
- Authorize with JWT and/or SigV4; policies are evaluated with ABAC (Cedar).
What we do not document here
Platform hosts, provisioning, and operator workflows are maintainer material — not part of the customer product surface.