Infrastructure
Scripts and flows
Built inWrite a script once, hang it under a plan, and every machine you deliver gets it.
Provibr does not decide what your machines look like after delivery. A script is text with variables in it: you write it, you preview it against a real server, and you can read exactly what would be sent before anything runs.
What you need
- Nothing. It is in every account, including during the trial.
- An agent, but only for the flows that actually deliver something to a machine
- An API key from your own profile page if you want to drive the same things from outside
What it does
This is not an integration you connect but a part of the platform, on in every account. A run records the template, the versions it used and the names of the secrets it read. It never records the rendered text, so a password does not end up sitting in a database.
Variables, snippets and secrets
Every documented property of a server, its plan, its addresses and its owner is available as a variable. Shared fragments become snippets you reuse, and keys and passwords live in a separate namespace that is encrypted at rest.
Flows that run on delivery
Hang a flow under a plan and it runs when a machine is handed over, or after a network installation. Each run keeps the template version and the version of every snippet it used, so a shared edit never rewrites what already happened.
Or drive it over the API
Everything the panel does has a REST endpoint behind it: create a machine, attach a disk, hand out an address. A script covers what happens on the machine, the API covers what happens around it, with a key you scope yourself.
Where this stands
Built into the platform. There is nothing to connect and nothing to install: scripts, snippets, secrets and flows are in every account from the first day of the trial.
Other integrations
PowerDNSStart with one host and one agent
Create an account, install the agent with a single command and connect your first Proxmox host. The trial runs for 14 days and asks for no payment details.