@alien

Add BYOC, on-prem, and more - and manage it all across 10k+ enterprises

 San Francisco, CA
alien.dev
Joined February 2026
  • Tweets43
  • Following1
  • Followers277
22Media
Alien AI Gateway is live! Route AI inference requests directly into your customers' own AI provider. Initial support for AWS Bedrock, GCP Vertex AI, Azure Foundry AI, Anthropic, OpenAI, Databricks
1
6
836
Alien KV now supports atomic conditional writes on DynamoDB, Firestore, and Azure Table Storage. Every read returns a version, and writes can require one.
1
2
684
Introducing Alien AI: Frontier models, running inside your customer's cloud → Prompts and data never leave their account → No API keys — calls run under the workload's own cloud identity → AWS Bedrock, Google Vertex AI and Azure Foundry from one line of stack code → Claude, GPT, Gemini, Mistral, Qwen, DeepSeek and dozens more Makes AI features shippable into regulated environments Their cloud, their models, their bill
1
2
6
377
Should I ship it?
2
3
323
Just shipped 8 new features and improvements👇
2
3
1
6
2,583
more replies
8. Team invitations You can now invite your team to a workspace - by email, or with an expiring invite link.
1
3
164
Visit our full changelog at alien.dev/changelog

Changelog

New features and improvements in Alien, newest first. The platform for deploying and operating your software in your customers' clouds.

alien.dev
2
108
Your BYOC app can now expose HTTPS endpoints directly from your customer's cloud: VPN-only: For internal dashboards and admin tools Private: For service-to-service APIs Public: For webhooks and external APIs Alien handles DNS, TLS, and load balancing automatically.
1
1
1
1,125
alien.dev/changelog/2026-07-…

Public endpoints

Named HTTPS endpoints for Workers, Containers, and Daemons, with DNS and TLS handled per deployment in the customer's cloud.

alien.dev
1
242
Alien Daemons let you run a managed process on every machine in a customer deployment. Use them for the work that should live on the machine: observability collectors, node agents, and host-level control loops.
1
1
1
10
1,169

AI is bringing on-prem back

Article · @alongubkin
1
6
420
In BYOC, don't move auth into the customer cloud. The best pattern is to keep dashboard, login, users, API keys, etc in the control plane. When a client need to access sensitive data, first exchange its normal session for a short-lived JWT scoped to that customer deployment, and then let the client communicate directly with the customer cloud using that JWT. The data plane can verify it locally and serve the data, without owning identity or secrets.
1
1
5
349
You can now provision a managed Postgres database directly inside your customer's cloud.
1
2
767
Load more