ProvidersComing in 1.1
Connect a vendor once. Use it everywhere.
Cloudflare, your DNS host, your registrar, your storage and your cloud. Save each connection once, tested before it is kept, and every part of the panel that needs it can use it.
Not available yet. This page shows what is being built, so you can plan around it.
What you connect
- Cloudflare
- DNS hosts
- Domain registrars
- Object storage
- Cloud servers
- Custom providers
How it works
Pick the vendor
Choose from the catalog. Each connect page has a short guide with the steps and the token scope to create.
Save and test
The panel makes one cheap call to the vendor first. A connection is kept only when that call works.
Use it
Domains, certificates, backups and servers use the saved connection. Rechecked every 15 minutes.
What you get
-
Cloudflare in full
Not only DNS records: the proxy and the rest of what you do at Cloudflare, from the panel.
-
DNS hosts and registrars
Edit records and nameservers where the domain lives, without a second login.
-
Storage
S3 compatible stores, Backblaze, Wasabi, R2, Spaces, Azure Blob, Google Cloud Storage, SFTP and WebDAV.
-
Custom providers
Not on the list? Describe the vendor's API by hand, or let the AI draft it from the API docs. You test and save it.
Keys are kept safe
- Secrets sit in the encrypted vault. The panel keeps only the last four characters in view.
- The AI reads a vendor's public API docs, never your key. It only drafts. You test and save.
- Outbound calls use HTTPS only and refuse private addresses.
In preview
In preview today
The first part is built and tested in our lab.
- 34 domain registrars and DNS hosts in the catalog, 26 with a native adapter and the rest through a custom definition
- Cloudflare DNS, with the token tested on save
- Custom providers described by hand, as data and never code
- Storage connections for backups
Questions
What is coming in 1.1?
Cloudflare beyond DNS, the shared connection page for clouds and storage, and AI drafted custom providers.
Does the AI see my keys?
No. It reads the vendor's public documentation and writes a draft. Keys stay in the vault.