Alien now provisions AI inference as a resource. Your product's AI features run on the model service already inside the customer's cloud — Bedrock on AWS, Vertex AI on GCP, AI Foundry on Azure — so the prompts, the data, and the bill all stay with them.

const llm = new alien.AI("assistant").build()

The model is an argument on each request, not a decision in the stack, so one stack file works across three clouds whose model menus differ:

const llm = ai("assistant")

// Model menus differ per cloud, so take one this deployment actually has.
const [model] = await llm.getAvailableModels()

const answer = await llm.chat.completions.create({
  model: model.id,
  messages: [{ role: "user", content: "Summarize this support thread." }],
})

• Prompts and data never leave their account — inference runs where the workload runs
• 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 — whatever that cloud serves
• The provider's real API, not a translation layer

That makes AI features shippable into regulated environments: their cloud, their models, their bill.

Some models need a one-time activation in the customer's cloud account before they can be called — Claude on all three clouds.

Read the docs →