Overview
Skippr Cloud gives you managed identity, application backends, data, messaging, web delivery, and infrastructure state. Call each capability with skippr <service> <operation> after skippr login. Service guides show the same provisionable creates as CLI, Terraform, CDKTF TypeScript, or CDKTF Python. Start with a capability below. Do not treat a documented stub as available yet.
At a glance
| Fact | Value |
|---|---|
| Status | Preview |
| Regions | eu-central-1 (more will follow) |
| CLI | skippr — install, then Get started |
| Shared API endpoint | https://api.cloud.skippr.io |
| Regional endpoint | https://{service}.{region}.cloud.skippr.io |
| Authentication | skippr login, or capability-scoped SigV4 credentials |
| Infrastructure as code | Terraform skippr/cloud; CDKTF TypeScript and Python |
| SDKs | crates.io skippr-cloud; npm @skippr/cloud; PyPI skippr-cloud |
| Browse services | Service catalog |
| Find an action | API action reference |
| Provision resources | Infrastructure resources |
Preview capabilities
Build and secure an application
| Capability | Use it to |
|---|---|
auth | Create app user pools for users of your product. |
| Cloud User Directory | Sign in, manage people on your account, attach policies, and create keys. |
secrets | Store and rotate named application secrets. |
gateway | Create HTTP or WebSocket Apis, routes, authorizers, and function or event integrations. |
functions | Register, update, and invoke short-lived application code. |
sites | Publish a website, promote or roll back a deployment, and bind a custom domain after DNS validation. |
deploy | Bind a GitHub App installation, create runner pools, and run GitHub Actions jobs on Skippr-managed Linux runners. |
Store and move data
| Capability | Use it to |
|---|---|
tables | Store document and key-value items with PK/SK keys, indexes, conditionals, transactions, and TTL. |
objects | Store objects, use multipart uploads, and create presigned URLs. |
queue | Hand work to competing consumers with visibility and acknowledgement controls. |
events | Route application events to queue and function targets. |
scheduler | Run named schedules that deliver to events or queue. |
logs | Ingest and filter application log events. |
metrics | Record datapoints, query aggregates, and manage alarms. |
traces | Ingest spans and look up traces. |
elt | Declare managed pipelines and inspect run status. The installable ELT runner is a separate Production product. |
Manage domains and infrastructure state
| Capability | Use it to |
|---|---|
dns | Manage zones, records, and DNS-01 validation records. |
certs | Request, inspect, renew, and delete public TLS certificates. |
inventory | See which Cloud resources exist in your account and whether they have drifted. |
Use skippr <service> --help or the API action reference to confirm an action is available and to open its request and response contracts.
Preview stubs
These capabilities are not available yet:
| Capability | Intended job |
|---|---|
streams | Ordered append log with topics, partitions, consumer groups, and offsets. |
machines | Long-running virtual machine fleets. |
Common journeys
Create an API-backed application
- Sign in with
skippr login, then use Cloud User Directory for people and workload identity. - Store application state with
skippr tablesand credentials withskippr secrets. - Register code with
skippr functions. - Expose HTTP or WebSocket routes with
skippr gateway. - Add asynchronous work with
skippr events,skippr queue, andskippr scheduler.
Publish a web application
- Create a stable
sitesSite. - Upload and complete an immutable Deployment.
- Test its preview hostname.
- Promote the Deployment and optionally attach a DomainBinding.
- Route dynamic application requests to a
gatewayApi.
Manage infrastructure as code
- Obtain operator or workload credentials from Cloud User Directory.
- Choose Terraform or CDKTF.
- Declare supported
cloud_*resources. - Use
inventoryfor managed-resource verification; keep Terraform as the source of desired state.
Limits, errors, and contracts
Limits are service-specific. Use each capability guide and API action schema rather than assuming a platform-wide value. Cloud JSON errors use code, message, and requestId.
The CLI is the default client. The API reference defines the shared HTTPS protocol for SDKs and direct callers, and links to the service catalog, API action reference, Infrastructure resources, and machine-readable schemas.
