Skip to content

Blog

Scaffolding Production Stacks with puls init

Starting a new Infrastructure-as-Code (IaC) repository can be intimidating. Often, developers are left staring at a blank terminal, wondering how to structure their directories, where to put environmental configurations, and how to link resources across different files.

To solve this, we have revamped the puls init command. Instead of dumping simple dummy files, puls init now bootstraps a production-ready, modular directory layout using a TypeScript-first configuration architecture.

Puls 1.0.0 Released: General Availability

Today, we are thrilled to announce the official release of Puls 1.0.0 - the first stable, production-ready version of our TypeScript-native cloud infrastructure framework.

Puls is not a configuration language and it is not a wrapper around Terraform. It is a framework: you write real TypeScript, import the providers you need, and Puls handles the gap between your declared intent and live cloud state on every run. Instead of state files and plan stages, Puls uses eager discovery - each deployment starts by reading the live cloud, computes the diff in memory, and reconciles immediately, in a single step. No lock files. No apply confirmation prompts. No drift between what the plan said and what actually happened.

Introducing Puls Importer: The Visual Interactive Cloud Migration Engine

Migrating legacy cloud infrastructure into modern Infrastructure-as-Code (IaC) is one of the most tedious, error-prone tasks in cloud engineering. Traditionally, developers had to manually inspect cloud consoles, copy resource IDs one by one, and write hundreds of lines of code from scratch.

To solve this, we are building Puls Importer - a visual, interactive cloud migration wizard that auto-discovers and maps cloud configurations directly into clean, modular TypeScript stacks.

Infrastructure as Code Without State Files (and Without the Headaches)

If you've managed cloud resources over the last decade, you've likely had a run-in with a state file.

Whether it's Terraform's .tfstate or Pulumi's stack state, traditional Infrastructure-as-Code (IaC) tools rely on a centralized ledger. This file is their source of truth-a mapping of declared resource names to physical cloud IDs, tracking metadata and dependencies.

While state files solved a major problem in the early days of cloud automation, they introduced a host of operational challenges that teams spend hundreds of engineering hours managing.

Puls is built around a different philosophy: what if we didn't need state files at all?

Dynamic Secret Injection: Zero-Hardcoding Credentials in Puls

Hardcoding credentials in your version control system is one of the most common ways security leaks happen. Whether it's an API token, a database root password, or a service account key, committing credentials to Git is a recipe for disaster.

Yet, managing these secrets on team projects is often painful. Developers end up sharing .env files via Slack, updating private vaults manually, or writing complex bootstrap scripts.

Puls solves this with Secrets at Deploy Time: a lazy-resolved, type-safe secret engine that fetches passwords directly from secure cloud vaults when deploying, with native injection into your VM environments and provisioning scripts.