distilled.cloud
Effect-native SDKs for cloud providers
Tagged errors. Retry policies. Streaming pagination.
Effect-native SDKs for cloud providers
Tagged errors. Retry policies. Streaming pagination.
Effect-native clients for major cloud providers, with tagged errors and tree-shakeable imports.
Complete AWS SDK with typed errors for S3, Lambda, DynamoDB, SQS, and 200+ services.
Azure Resource Manager SDK for Compute, Storage, Network, SQL, and 200+ services with typed errors.
Cloudflare API client for Workers, R2, KV, D1, Queues, and more with complete error coverage.
Coinbase API client with typed errors for accounts, transactions, and exchange operations.
Fly.io platform API client for apps, machines, volumes, and secrets management.
Google Cloud Platform SDK for Cloud Storage, Functions, BigQuery, and Firestore with typed errors.
MongoDB Atlas API client for clusters, databases, and project management with typed errors.
Neon serverless Postgres client with branching, autoscaling, and complete error coverage.
PlanetScale MySQL serverless database client with type-safe queries and error handling.
Prisma Postgres managed database client with typed operations and error handling.
Stripe payments API client with typed errors for charges, subscriptions, and webhooks.
Supabase platform API client for projects, databases, auth, and storage with typed errors.
Turso edge SQLite database client for databases, groups, and organizations with typed errors.
The Problem
Every cloud provider ships incomplete specs. Errors are discovered at runtime, not compile time.
APIs return cryptic error codes that aren't in the documentation. You only discover them in production.
OpenAPI and Smithy specs are missing properties, wrong types, or outdated. The docs lie.
Errors you can't catch because they're not in the types. Your "exhaustive" switch statement isn't.
Import one function, bundle hundreds. Class-based SDKs can't tree-shake.
Effect-native cloud SDKs for modern TypeScript
Every API operation has properly typed, discriminated error unions. No more guessing what went wrong.
Declarative, composable retry logic with type-safe schedules. Handle transient failures without callback hell.
Paginated APIs return Effect Streams. No manual token juggling—just iterate.
Upload and download with Effect Streams. Process data as it flows without buffering entire payloads.
No monolithic client classes. Import only what you need—your bundle stays lean.
The Mission
Type-safe, tagged error specs aren't just good for developers—they're essential for AI code generation.
distilled SDKs are built to power alchemy.run—next-generation Infrastructure-as-Code in native TypeScript. When AI generates infrastructure code, it needs to know every possible error and how to handle it.
Proper error tags mean sound, reliable tooling. No more hallucinated error handling. No more runtime surprises.
GitHub