CLI 1.0.12 adds stackshift setup agent to install project-local StackShift guidance. Setup pages cover Codex, Claude Code, Cursor, VS Code, Gemini CLI, Windsurf and OpenCode, with installation commands and example prompts. The public prompt.md offers an agent-led setup path. Installing guidance does not deploy your project or grant cloud access.
StackShift skills guide coding agents through existing repositories, supported deployment paths, environment configuration, readiness checks and recovery. The guidance also covers applications using databases, Assets, S2 and Mail, preserving existing services unless you request a migration.
Authorize your coding agent to work with selected StackShift resources and permitted actions. Review connection access, expiry and recorded activity, approve requested changes, and revoke access when needed. External-agent reasoning stays with its provider; connecting an agent does not transfer its subscription into StackShift chat.
Organize work in agent conversations with objectives, questions, approvals and operation history. Follow requested changes through their recorded results and inspect the affected resources. Deployment and runtime checks remain separate from the agent conversation, so a completed message alone does not establish that an application is healthy.
Define owner policies for permitted actions and environments, and manage recurring agent work through assignments and schedules. Actions remain subject to the applicable scope, expiry and approval requirements. Review operation history to see what ran and what still needs attention.
Manage AI credits and choose funding preferences for Assets, agents and workflows. Add supported provider API keys and explicitly select their use. Adding a key does not silently change funding, and connecting an external coding agent does not remove the funding requirements for native StackShift AI tasks.
Publish an HTTP service running on a full-root VPS at a StackShift HTTPS address, including on IPv6-only VPSs. Choose the guest port in Publishing, then add a verified custom domain if you want to use your own name. Existing apps, direct IP access, and domains stay in place unless you choose to change them.
Enable an SSH endpoint for a VPS from its Publishing tab and connect through ssh.compute.stackshift.cloud using its assigned port. Keep the same guest login and SSH key. This gives IPv6-only VPS owners an SSH path from networks that cannot reach IPv6 directly, without assigning the guest a dedicated public IPv4 address.
IPv6-only Compute VPSs can reach IPv4-only services through shared outbound IPv4 connectivity while keeping their public IPv6 identity. Inbound access remains separate: use Edge SSH for remote login or web publishing for an HTTPS app address.
Hosted customer execution now uses digest-bound admission receipts, immutable image evidence, restricted outbound networking, exact external-service grants, private-route approvals, runtime flow monitoring, and durable quarantine. Project owners can inspect policy, dependencies, grant expiry, and incidents from the dashboard, CLI, SDKs, and API, while operators review sensitive decisions through a separate security queue.
Containerd and Kata workloads now join application-scoped CNI networks through StackShift’s internal bridge. Source-aware internal DNS resolves stable service names only inside the correct application network, while NetGuard enforces project bindings, private-service access, host protection, metadata blocking, and controlled egress at the packet layer.
StackShift Mail now brings transactional delivery, OTP flows, SMTP submission, scheduled and batch sends, inbound mail, templates, streams, audiences, campaigns, delivery timelines, webhooks, suppression handling, diagnostics, analytics, and exports into one first-party platform. The refreshed dashboard and documentation make message progress and deliverability easier to inspect.
StackShift Assets now supports deterministic media transforms, governed workflow graphs, approvals, reusable connections, run history, retries, webhooks, Stackie actions, and MCP tooling. Typed configuration keeps common workflow setup accessible while preserving an advanced canonical contract for automation and SDK users.
StackShift Sandbox provides isolated, disposable workspaces with repository-backed files, terminals, agents, previews, browser sessions, temporary databases, snapshots, sleep and resume, and deployment handoff. The same API-first lifecycle supports interactive development and automated code-execution workflows.
StackShift S2 now combines its S3-compatible object interface with access keys, bucket policies, usage visibility, audit events, lifecycle operations, integrity checks, backups, restore workflows, and off-server recovery. Applications keep the same storage contract as the underlying topology evolves.
The StackShift CLI now covers more of the platform’s application, database, S2, Assets, workflow, Sandbox, Compute, domain, and operational surface. Signed releases are available for macOS, Linux, and Windows, with generated command references kept aligned with the customer API.
Connected servers and customer-cloud nodes now use ten-minute single-use enrollment, signed OS and architecture-qualified bootstrap profiles, WireGuard-only agent access, rotating SPIFFE-style mTLS identities, and node-scoped registry grants. BYOCloud supports Hetzner and DigitalOcean scoped tokens, AWS assumed roles with external IDs, and Azure workload federation, with durable idempotent provisioning, reconciliation, volumes, snapshots, stable IPs, reboot, retry, and provider-confirmed safe deletion. The CLI, Terraform provider, dashboard, and Mintlify documentation expose the same clean contract.
Qualified hosted V2 databases can now export portable SQL or compressed SQL and import .sql or .sql.gz from a resumable browser upload or hardened HTTPS URL. Imports restore into a hidden private candidate for structural validation and read-only inspection before explicit promotion; cutover keeps the stable hostname, credentials, TLS, and public-access policy unchanged, with the prior generation retained read-only for a 24-hour rollback window. Available on every active plan.
The Assets platform now documents and exposes resumable uploads, revision-safe mutations, image transforms, video HLS outputs, signed delivery, AI jobs, versions, branches, collections, webhooks, and usage summaries across the JavaScript, Python, and Go SDKs.
The Mintlify docs now include a grounded Assets API reference plus implementation guides for direct browser uploads, private files, image optimization, DAM workflows, video governance, AI processing, and versioned delivery.
CI/CD for your mobile releases — define a YAML pipeline in your repo that builds, waits for approval, submits to the stores, publishes over-the-air updates, and runs your own scripts, triggered by tags, pushes, schedules, or a button.
Crashes and errors from your production app, grouped by cause with symbolicated Android stack traces, crash-free rates per version and per OTA update, and alerts by email or webhook. SDKs for React Native, Expo, and Flutter.
Publish Expo and React Native JS updates without your own CI — the build infrastructure exports the bundle and ships it to a channel in one pipeline step.
Build signed Android and iOS binaries from GitHub on every tag, then submit them to Google Play and the App Store with listing metadata, screenshots, and privacy details managed from one place.
Full docs at docs.stackshift.cloud — including native WordPress, multisite networks, and importing an existing site.
Builds compile straight to BuildKit instead of generating a Dockerfile — quicker, with fewer moving parts.
Distribute iOS and Android builds to testers and users — release channels, staged rollouts, approval gates, tester feedback, CI upload tokens, and public install links.
Stackie now diagnoses failed builds and degraded apps, writes the fix, and redeploys — you click apply.
Manage StackShift as code — an official provider on the Terraform Registry with resources for projects, databases, domains, DNS, buckets, compute, and more.
S3-compatible buckets with CDN delivery, provisioned alongside your app and wired up automatically.
Run commands against your apps and nodes from the browser — with scoped permissions, production safeguards, and recorded sessions.
Manage WordPress sites for multiple clients from one place, each with its own control surface and releases.
Added C#/.NET, Bun, and TanStack Start, plus drag-and-drop to organize projects.
Refreshed email templates and one-click List-Unsubscribe for better deliverability.
Spin up VPS instances next to your apps for full control when you need it.
Transactional email, object-storage assets, and a durable background-job runner — all built in.
WordPress runs on a native runtime with an auto-provisioned managed MySQL database — no hand-rolled containers.
Connect your own servers and deploy to them through the same StackShift control plane.