Domains and DNS
Let automation inspect or change exactly what is approved without making a vendor your permanent registrar administrator.
A very convenient way to lose leverage
The AI asked for your keys.You gave it the keyring.
Domain admin. Email admin. Billing admin. Production credentials. Apparently "connect your business" meant all of your business.
Interactive mini-commercialAbout 30 secondsNo real credentials used
Before the key handoffSimulation
Meet your new AI vendor
To be helpful, it just needs your domain admin, email admin, billing admin, production token, and the password you swore you would never reuse.
Connect your businessFull access requested
DNSRegistrar + nameserver administration
EmailOrganization administrator
BillingPayment + subscription administration
ProdPersistent production credential
Fast setup is great right up until the vendor becomes part of your root-of-trust.
Fictional demonstration only. No credentials, vendors, accounts, DNS zones, or production systems are connected.
The joke has a root password
Use the tool.Keep custody.
INTIGNAI treats useful context and credential authority as different things. The goal is not to make AI powerless. It is to give it the smallest capability that can do the approved job while root credentials remain under your control.
The AI can use a capability.It does not need to own the credential.
Where this stops being funny
Vendor lock-in is annoying.Credential lock-in is authority.
Email administration
Separate mailbox help from organization-wide admin authority, exports, forwarding rules, and identity control.
Billing and commerce
AI can prepare the work around money without inheriting reusable authority to charge, refund, or change payment configuration.
Production systems
Prefer scoped, expiring capabilities and receipts over persistent root tokens copied into another vendor dashboard.
Do not start by migrating everything.
Pick one keyyou refuse to hand over.
We can map the exact credential, capability, approval, expiry, and receipt boundary around one real workflow first. No passwords. No secret values. No production connection required to start.
The first step is a Control Map, not a credential transfer. Describe the system and authority boundary in plain language. Do not include passwords, API keys, private customer records, or other secrets.
Put AI to work. Keep the authority.