Stack vs Pulumi

TL;DR

Compare Stack with Pulumi against the workflow you need. Stack coordinates provider setup: four adapters have resource-creation paths, while others attach to existing resources or accept credentials. Credential storage and .mcp.json updates are sequential and conditional; Stack does not automatically generate a filled .env. Check current Pulumi documentation for its supported infrastructure and integration contracts.

When to pick each

Pick Pulumi when	Pick Stack when
Check current provider support for the cloud resources you need.	You want coordinated setup for supported SaaS adapters.
Check environment, region, state and drift requirements.	You want to evaluate stack add supabase with authorized provider and Phantom setup.
Verify the vendor’s current compliance and audit controls.	You want source-defined CLI, MCP and plugin workflows.

Choose based on the resources, credentials and configuration your workflow actually needs. stack add stripe accepts an existing credential; it does not create a Stripe account. Qualify each adapter before relying on provider setup.

At-a-glance

Capability	Stack	Pulumi
Category	SaaS control plane	Check current product scope.
Primary surface	CLI + MCP server + Claude Code plugin	Check supported CLI and language interfaces.
What it provisions	39 catalog entries; four adapters have create-resource paths, others attach or accept credentials.	Check current resource and provider coverage.
Describes state with	.stack.toml declarations plus local instance metadata; managed credential slots use Phantom.	Check current state-storage and backend contracts.
Secrets handling	Sequential Phantom credential writes; no automatic filled .env or safe-to-commit token guarantee.	Check current secret-storage and delivery guarantees.
AI surface	Native stack recommend + MCP tools + Claude Code plugin	Check current agent and AI interfaces.
OAuth automation	Configured OAuth or PAT/API-key paths, depending on the adapter.	Check credential prerequisites for the selected provider.
License	MIT source 0.2.1; recorded public npm 0.1.1 is a separate artifact.	Check current license and commercial terms.
Free tier	MIT source; no future pricing guarantee.	Check current pricing and limits.
Best for	SaaS composition, agentic workflows, Claude Code users	Evaluate against your infrastructure and compliance requirements.

Where they overlap

The overlap to evaluate is provider setup and configuration management. Stack has a 39-entry source catalog, but catalog membership does not mean every adapter creates a resource. Inspect the selected adapter and the other tool’s current documentation before choosing an integration.

Where Stack wins

Source-backed Stack capabilities to evaluate:

• Conditional resource creation. stack add supabase can create a project using the selected adapter and authorized account. Creation, credential storage and later configuration can fail separately; inspect the resulting state.
• Adapter-specific login. Some adapters use configured OAuth paths; others accept PATs or API keys. Verification strength varies, and a configured OAuth app is a prerequisite for its flow.
• MCP control plane. Reviewed source declares 19 tools that forward CLI output as text. stack_recommend, stack_add and stack_doctor have separate effects and failure boundaries. Check the installed client’s actual tool list.
• Local configuration. Stack separates .stack.toml declarations from local instance metadata and uses Phantom for managed credential slots. Project-supplied metadata is not automatically safe to commit.

Where Pulumi wins

Requirements to check against current Pulumi documentation:

• Cloud resource requirements. Stack’s AWS and GCP adapters do not create VPCs, subnets, IAM roles or RDS databases. Check the other tool’s current provider support for those needs.
• Environment and state requirements. Evaluate region, environment, drift and state-management requirements against actual installed interfaces. This page does not qualify a multi-tool deployment.
• Compliance requirements. Verify current certifications, access controls and audit behavior directly with the vendor. Stack source and an MIT license do not establish those controls.
• Existing workflows. Preserve a working deployment while evaluating changes. A Phantom-to-ESC credential bridge is not implemented or qualified by this Stack source.

Can I use both?

You can evaluate separate workflows. A possible division to qualify:

• Pulumi should be evaluated against the infrastructure resources, permissions and state requirements of your project.
• Stack coordinates supported provider setup and configuration. It does not take ownership of every SaaS account or delete upstream resources on removal.

No native hand-off to Pulumi ESC is established by this source. Review the Phantom integration and the installed interfaces for credential delivery. stack doctor reports available checks; unchecked services and a zero exit are not proof that the combined application works.

Migration and caveats

This page describes reviewed Stack source 0.2.1. Recorded public npm 0.1.1 and historical native release 0.2.0 are separate artifacts. The roadmap describes proposals, not installed capabilities. Browse the 39-entry source catalog and qualify the installed adapter you intend to use.

FAQ

Does Stack replace Pulumi?

Stack coordinates supported provider setup and Phantom credential storage. Supabase, Neon, Turso and Vercel have resource-creation paths; other adapters attach to existing resources or accept credentials. Compare Pulumi's current documentation against your infrastructure requirements rather than treating this page as a vendor feature audit.

Can I use Pulumi and Stack together?

You can evaluate separate workflows, but this source does not establish a native Pulumi-to-Stack or Phantom-to-ESC bridge. Qualify credential delivery, configuration and permissions for each tool before combining them.

Why doesn't Stack just use the Pulumi SaaS providers?

Stack’s reviewed source offers provider setup, sequential credential and configuration writes, conditional .mcp.json descriptors and available doctor checks. It does not prove Pulumi provider coverage or feature superiority.