November 2026 Summaries
4 posts from Zerops
Filter
Month:
Year:
Post Summaries
Back to Blog
Zerops’ showcase deployment example demonstrates how GitHub Actions can provision, update, and remove complete isolated environments containing an application, Python worker, PostgreSQL database, Valkey cache, NATS queue, and object storage for feature branches and pull requests. Each preview project has its own services and data, avoiding conflicts with staging systems and enabling end-to-end testing of uploads, background processing, migrations, and integrations, while persistent stage and production projects retain their infrastructure across application releases. The workflow maps Git events to named Zerops projects, selects source branches independently for the app and worker repositories with default-branch fallbacks, creates infrastructure only once per project, and subsequently deploys new application versions to existing services. A shared import template defines the service stack, while environment-specific values control resource sizes for development, staging, production, and previews. The example also emphasizes managing costs and security through minute-based resource awareness, automated cleanup on PR closure or branch deletion, an hourly sweep for missed events and expired previews, safeguards against deleting stage or production, environment-level deployment locks, and restricted credentials for trusted workflows.
Nov 12, 2026
1,233 words in the original blog post.
Zerops has expanded its platform with new infrastructure-as-code providers for Terraform/OpenTofu, Pulumi, and Alchemy, enabling teams to define, review, and apply project and service configurations through familiar workflows, while explicitly selecting managed-service modes such as single-node or high-availability PostgreSQL. Projects can now be deployed in EU Central, US East, or the newly added US West region. Box, now in open beta, provides Firecracker microVM sandboxes that can be created, paused, resumed, snapshotted, and forked with running processes preserved, though workspace data is not yet backed up. Development of the Zerops Control Plane (ZCP) continues with upcoming Mate capabilities for proposing staging, production, and MCP-server changes, alongside guidance to isolate production projects from ZCP-enabled environments. Recent zCLI releases added upgrade checks, asynchronous deployment options, browser login, and sudo mode, while Swarm offers application-controlled pools of containers or VMs for tasks such as CI jobs. Zerops has also expanded recipes, challenge resources, and GitHub Actions examples for preview environments that provision complete application stacks and automatically clean up branch or pull-request deployments.
Nov 12, 2026
984 words in the original blog post.
Zerops supports Terraform, Pulumi, and Alchemy providers for defining, previewing, deploying, and maintaining an application stack as code, illustrated through a Node.js 22 API connected privately to PostgreSQL 16, Valkey 7.2, and a 1 GB object-storage bucket, with a public HTTPS route. Terraform provides an explicit HCL resource graph and works with Terraform or OpenTofu, while Pulumi bridges the Terraform provider into programming languages such as TypeScript and Alchemy combines application source, runtime configuration, environment variables, and infrastructure in an application-focused TypeScript/Effect workflow. All approaches use Zerops service references for database, cache, and storage credentials, require explicit dependency handling or typed references, and were tested to return successful responses without subsequent drift. The comparison emphasizes secure state and credential management, reviewed plans, immutable source revisions, serialized CI deployments, and distinct rollback versus infrastructure-destruction procedures. Terraform or OpenTofu is positioned for established infrastructure-as-code workflows, Pulumi for language-based infrastructure with shared provider coverage, and Alchemy for stacks where application code and service configuration should remain closely integrated, although Alchemy currently lacks some capabilities such as dedicated IPv4, VPNs, general lookups, and certificate-issuance waiting.
Nov 12, 2026
1,749 words in the original blog post.
Box is an open-beta Zerops service for running agent-written code in Firecracker microVM sandboxes hosted inside a workspace VM within the user’s project, placing execution close to private applications, databases, queues, and other services. The overview compares sandbox approaches across providers, including Firecracker microVMs, shared-kernel containers, gVisor, and alternative VM monitors, emphasizing differences in isolation, hardware support, networking, and whether paused or restored environments retain files, memory, and running processes. Box’s notable capabilities include parking sandboxes by saving their memory state, waking them with processes resumed, and forking active environments so copies retain running processes and then diverge independently. Workspaces provide shared CPU, memory, and disk pools, configurable CPU overcommit, per-sandbox policy limits, templates, network modes ranging from project-and-internet access to air-gapped operation, and egress restrictions. Sandboxes can access project-private services by default, expose internal HTTP or WebSocket ports, and use secret-delivery options that restrict forking or snapshots when plaintext credentials are present. Box supports CLI, web console, HTTP API, and MCP integration, with Ubuntu-based templates and common development tools, while noting that Docker-in-sandbox support and automatic workspace data backups are not yet available.
Nov 12, 2026
2,052 words in the original blog post.