Skip to main content
[envilder]
  • Features
  • How it works
  • Providers
  • Changelog
  • Docs ›
    • Get started
    • CLI pull
    • .NET SDK
    • GitHub Action
    • Map file
Get Started

Getting started

  • Get started

Providers

  • AWS SSM
  • Azure Key Vault

CLI

  • Map file
  • CLI pull
  • CLI push

GitHub Action

  • GitHub Action

SDKs

  • .NET SDK
  • Python SDK
  • Node.js SDK
Home/Documentation

Envilder documentation

Choose a guide to configure Envilder, resolve secrets, or load them at runtime.

Get started with Envilder

Install the CLI, review prerequisites, and understand the mapping model.

Open guide

AWS SSM setup

Configure AWS credentials and the permissions Envilder needs.

Open guide

Azure Key Vault setup

Configure Azure authentication and Key Vault permissions.

Open guide

Map file reference

Map variables to secret paths and configure the selected provider.

Open guide

CLI pull command

Generate a .env file from secrets defined in your map file.

Open guide

CLI push command

Upload a mapped .env file or one secret to your provider.

Open guide

GitHub Action guide

Configure the action for AWS, Azure, and multiple environments.

Open guide

.NET SDK guide

Install and use the .NET runtime SDK.

Open guide

Python SDK guide

Install and use the Python runtime SDK.

Open guide

Node.js SDK guide

Install and use the Node.js runtime SDK.

Open guide
[envilder]

One configuration model to resolve secrets consistently across environments and runtimes. Powered by your existing cloud infrastructure.

MIT Licensev0.13.2

Project

  • GitHub
  • npm
  • Changelog
  • Roadmap

Documentation

  • Getting Started
  • Pull Command
  • Push Command
  • GitHub Action

Community

  • Issues
  • Discussions
  • Security
  • Sponsor
ENCAES

© 2026 macalbert.Built with Astro. Open source on GitHub.