Code you can use

Ready-made code for the InfraNest API, open source on GitHub. Copy it, change it, run it — at your own risk, as each repository's licence says.

Examples

infranest-examples — the recipes as scripts you can run, in shell, Python, Node.js and PowerShell: dynamic DNS, Let's Encrypt DNS-01 hooks, a maintenance window around a deploy, a monitor per deploy, watching a new server, the audit log to a SIEM, and a smoke test for your sandbox. Every request in them is checked against the API description, so they keep working as the API grows.

GitHub Action

InfraNest Maintenance Window (source) — silence alerts while a workflow deploys, and turn them back on afterwards. It also pauses and resumes a monitor and resets your sandbox.

- uses: InfraNest-Infrastructure-Organized/infranest-action@v1
  id: window
  with:
    token: ${{ secrets.INFRANEST_TOKEN }}
    organization: 12
    command: maintenance-open
    minutes: 30

See Maintenance from a pipeline for the whole workflow.

OpenAPI description

infranest-openapi — the API description as a versioned file, updated daily from developers.infranest.io/openapi.json, with a dated release whenever it changes. Point a client generator, Postman or an API gateway at it, or watch the repository to hear about new endpoints.

Server agent

infranest-agent — the agent that sends a server's metrics to InfraNest. It runs unprivileged, and its source is public so you can read exactly what it does on your machines. See Install on many servers.

AI assistants

Ask Claude, Cursor or VS Code about your infrastructure through the hosted MCP server.

Found a problem?

Open an issue in the repository it is about. Report a security problem privately, as each repository's SECURITY.md explains — never in a public issue.