The fast builder's toolkit β less managing, more making
Tired of bouncing between registrars, tracking domain renewals in spreadsheets, and copy-pasting secrets into .env files?
π― indietool is the fast builder's toolkit β less managing, more making. It helps you
- π Hunt domain names across 50+ TLDs β in seconds
- ποΈ Track expiries across registrars like Cloudflare & Porkbun
- βοΈ Manage DNS records across providers with auto-detection
- π Securely store API keys & secrets β OS keyring or SSH-key encrypted
No dashboards. No vendor lock-in. Just you and your terminal.
Demo:
domain explore->domains list->dns set->secret getin under 30 seconds
# Homebrew (recommended)
brew install indietool/tap/indietool
# Go
go install github.com/indietool/cli@latest
# Binary releases (macOS, Linux, Windows)
# Download from https://github.com/indietool/cli/releases
# Shell completions
indietool completion bash > /usr/local/share/bash-completion/completions/indietool
indietool completion zsh > /usr/local/share/zsh/site-functions/_indietool
indietool completion fish > ~/.config/fish/completions/indietool.fish# Check domain availability (no API keys needed!)
indietool domain explore myapp
# Save a test API key (auto-creates encryption key)
indietool secret set stripe-key "sk_test_..." --note "Stripe test key"
# Manage DNS records with automatic provider detection
indietool dns list example.com# Check which domains are available
indietool domain explore myproject --tlds dev,com,ai
# Set up DNS records for your new domain
indietool dns set myproject.dev @ A 192.168.1.100
indietool dns set myproject.dev www CNAME myproject.dev
indietool dns set myproject.dev api A 192.168.1.101
# Store your API keys securely (auto-creates encryption key)
indietool secret set openai-key "sk-..." --note "OpenAI API key"
indietool secret set stripe-key "sk_test_..." --note "Stripe test key"
# Organize secrets by project using custom databases
indietool secret set api-key@myproject "key123" --note "Project-specific key"# Check domain expiry before renewal
indietool domains list --provider cloudflare
# Verify DNS configuration before going live
indietool dns list myproject.com --wide
# Clean up old DNS records
indietool dns delete myproject.com old-api A
# Update production DNS records
indietool dns set myproject.com @ A 203.0.113.10
indietool dns set myproject.com www CNAME myproject.com
# Export secrets for deployment
export OPENAI_KEY=$(indietool secret get openai-key -S)Problem: Manually checking domain names is slow and painful.
Solution: indietool domain explore checks 50+ TLDs in seconds.
indietool domain explore awesomeprojectDOMAIN STATUS TLD EXPIRY
awesomeproject.ai Available ai -
awesomeproject.dev Available dev -
awesomeproject.com Taken com 2026-07-06
...
50 domains checked: 45 available, 5 taken
Filter by specific TLDs:
indietool domain explore awesomeproject --tlds ai,dev,io,shOr pass a TLD list from file:
indietool domain explore myproject --tlds @tldfileKnow the exact domain you're targeting?
indietool domain search awesomeproject.ioProblem: Domains expire. You don't want surprises. Solution: View all domains across registrars in one simple table.
First, connect your registrar(s):
# Cloudflare
indietool config add provider cloudflare \
--account-id YOUR_ACCOUNT_ID \
--api-token YOUR_TOKEN \
--email your@email.com
# Porkbun
indietool config add provider porkbun \
--api-key YOUR_KEY \
--api-secret YOUR_SECRET
# The Little Host (DNS only)
indietool config add provider thelittlehost --api-key tlh_YOUR_API_KEYThen list your domains:
indietool domains listNAME PROVIDER STATUS EXPIRES AUTO-RENEW AGE
myawesomeapp.com cloudflare healthy 8mo Yes 2y
sideproject.ai cloudflare healthy 1y Yes 1y
Need more info?
indietool domains list --wideNAME PROVIDER STATUS EXPIRES AUTO-RENEW AGE NAMESERVERS COST UPDATED
myawesomeapp.com cloudflare healthy 8mo Yes 2y fred.ns.cloudflare.com,pam.ns.cl... N/A 2y
sideproject.ai cloudflare healthy 1y Yes 1y fred.ns.cloudflare.com,pam.ns.cl... N/A 1y
Problem: Buying a domain means leaving the terminal, and renewal settings rot.
Solution: indietool wraps the new Cloudflare Registrar API β real-time availability checks, guarded registration, and auto-renew management.
Prerequisites on your Cloudflare account:
- Account ID β now required when configuring the provider (
--account-id) - API token with Registrar write permission
- A default payment method on the account
- A default registrant contact and the Domain Registration Agreement accepted (dashboard β Domains/Registrations)
# Configure Cloudflare with your account ID
indietool config add provider cloudflare \
--account-id YOUR_ACCOUNT_ID \
--api-token YOUR_TOKEN
# Real-time availability + price (beta API, up to 20 domains)
indietool domain check myapp.dev
indietool domain check myapp.com myapp.dev myapp.app --json
# Register a domain (billable β shows the price and asks you to confirm)
indietool domain register myapp.dev
indietool domain register myapp.dev --yes # skip the confirmation prompt
indietool domain register myapp.dev --dry-run # price check only, no purchase
# Renewal info + auto-renew toggle (new Registrar API)
indietool domains renew myapp.dev
indietool domains renew myapp.dev --on
indietool domains renew myapp.dev --off
# Full details: expiry, status, auto-renew, lock, privacy mode
indietool domain get myapp.dev
# Toggle auto-renew
indietool domain set myapp.dev --auto-renew --on
# (privacy/lock are dashboard-only; see notes below)Notes:
- All commands in this section use the new Cloudflare Registrar API (
/registrar/domain-check,/registrar/registrations, ...). The legacy/registrar/domainsendpoints are deprecated by Cloudflare (end-of-life 2026-09-27) and are not used. - Only a subset of TLDs is supported by the API beta; renewals, transfers, and contact updates are not yet available through it.
- Registration is billable and non-refundable β
indietoolalways shows the price and requires confirmation unless--yesis given. - API registrations default to
auto_renew: off; enable it withindietool domains renew <domain> --on. - Renewal pricing is not exposed by the API, and manual early renewal (paying to extend before expiry) is dashboard-only; the API manages auto-renewal only.
- Privacy & registrar lock are dashboard-only: the API currently supports updating
auto_renewonly, sodomain set --privacy/--lockedfails fast with an error instead of silently doing nothing.
Porkbun's API v3 supports the same registrar flow, paid from your Porkbun account credit:
# Configure Porkbun (API key + secret from porkbun.com/account/api)
indietool config add provider porkbun --api-key pk1_... --api-secret sk1_...
# Real-time availability + price (one domain per request; paced to Porkbun's
# check rate limit, default 1 per 10 seconds)
indietool domain check myapp.com --provider porkbun
# Register (billable, synchronous, charged to account credit)
indietool domain register myapp.com --provider porkbun --yes
# Renewal pricing + auto-renew toggle
indietool domains renew myapp.com --provider porkbun
indietool domains renew myapp.com --provider porkbun --on
# Full details: expiry, status, auto-renew, lock, privacy
indietool domain get myapp.comPorkbun notes:
- Test for free with sandbox keys β create
pk1_sb_/sk1_sb_keys at porkbun.com/account/api and add them as the provider credentials: the sandbox is a fully simulated account with fake credit on the same API. - Registrations use the account's default registrant contact; the API takes no contact fields, so
--contact-*flags are refused for--provider porkbun. - Premium domains cannot be registered via the API and are reported as not registrable by
domain check. - The account must be email/phone verified, hold sufficient credit, and have placed at least one prior registration (Porkbun requirement).
- WHOIS privacy and registrar lock have no API endpoints:
domain set --privacy/--lockedfails fast; manage them in the Porkbun dashboard. - Without
--provider, the first configured purchase-capable provider (cloudflare, then porkbun) is used.
Problem: Managing DNS records across different providers is tedious and error-prone.
Solution: indietool dns automatically detects your DNS provider and lets you list and update records from the command line.
# Auto-detect provider and list records
indietool dns list example.comDNS Provider: cloudflare
TYPE NAME CONTENT
A @ 192.168.1.1
A www 192.168.1.2
CNAME api example.com
MX @ 10 mail.example.com
Note: Cloudflare proxied records are indicated with a cloud icon, available only with the Cloudflare provider, for domains hosted on Cloudflare
indietool dns list example.com --wideTYPE NAME CONTENT TTL PRIORITY ID
A @ 192.168.1.1 300 abc123
A www 192.168.1.2 300 def456
CNAME api example.com 300 ghi789
MX @ mail.example.com 300 10 jkl012
# Add an A record
indietool dns set example.com www A 192.168.1.100
# Add MX record with priority
indietool dns set example.com @ MX "10 mail.example.com" --priority 10
# Add TXT record for domain verification
indietool dns set example.com @ TXT "v=spf1 include:_spf.google.com ~all"# Delete specific record by name and type
indietool dns delete example.com www A
# Delete all records for a name (with confirmation)
indietool dns delete example.com api
# Delete specific record by ID (when multiple records have same name)
indietool dns delete example.com test --id abc123
# Delete without confirmation
indietool dns delete example.com www A --force
# Delete root domain record
indietool dns delete example.com @ MX
# Combine filters for precision
indietool dns delete example.com api --type CNAME --id def456# Use specific provider instead of auto-detection
indietool dns list example.com --provider cloudflare
indietool dns set example.com api A 192.168.1.50 --provider porkbun
indietool dns delete example.com old-record A --provider namecheap- Cloudflare - Full CRUD operations with proxy status indicators
- Porkbun - Complete DNS record management (list, set, delete)
- Namecheap - Full CRUD support with batch operations
- The Little Host - Full DNS record management
indietool automatically detects your DNS provider by checking nameservers:
- No need to specify
--providerin most cases - Seamlessly works across different providers
- Falls back to manual provider selection if needed
Problem: Secrets are either insecure or annoying to manage.
Solution: indietool secrets encrypts secrets using your OS keyring β no cloud, no sync, no complicated setup to manage.
| Component | Backend | Stored At | Encrypted |
|---|---|---|---|
| Secrets Database | both | ~/.config/indietool/secrets/ |
β |
| Encryption Key | keyring | OS Keychain / gnome-keyring | β |
| Encryption Key | age-ssh | ~/.config/indietool/keys/db-key-<database>.age |
β |
indietool supports two backends for storing the database encryption key:
- keyring (default) β uses your OS keyring. Works well for desktop sessions.
- age-ssh (recommended for servers / SSH sessions) β encrypts the key with your SSH public key and stores it as a file. Decryption uses your SSH private key or agent.
# Explicit initialization with age-ssh (recommended for remote hosts)
indietool secrets init --backend age-ssh
# Specify a custom SSH key pair
indietool secrets init --backend age-ssh \
--ssh-public-key ~/.ssh/id_rsa.pub \
--ssh-private-key ~/.ssh/id_rsa
# Explicit initialization using the OS keyring
indietool secrets init --backend keyringIf indietool detects that the keyring is unavailable (e.g. in an SSH session), it will guide you through selecting an SSH key automatically on first use.
No setup required! The first time you store a secret, indietool automatically creates an encryption key.
indietool secret set stripe-key "sk_test_..." --note "Stripe test key"
Auto-generated encryption key for database 'default'
Secret 'stripe-key' stored successfullyUse the key@database format to organize secrets by project or environment:
# Store in custom databases
indietool secret set api-key@production "prod_key_123"
indietool secret set api-key@staging "staging_key_456"
indietool secret set db-password@myproject "secret123"
# Retrieve from specific database
indietool secret get api-key@production -S# Safe output (masked)
indietool secret get stripe-key
# Show actual value (use -S or --show)
indietool secret get stripe-key -S# List secrets in default database
indietool secret list
# List secrets in specific database
indietool secret list @production
indietool secret list @stagingList all your secret databases:
indietool secrets db listAvailable secrets databases:
default (default)
production
staging
myproject
Delete a database and all its secrets:
# Interactive confirmation
indietool secrets db delete staging
# Force delete without confirmation
indietool secrets db delete staging --force# Inject secret into command
indietool secret exec stripe-key -- curl -H "Authorization: Bearer *** https://api.stripe.com/v1/charges
# Use in environment variable
export STRIPE_KEY=$(indietool secret get stripe-key -S)
# Machine-readable output (global flag)
indietool version --json
indietool dns list example.com --json
indietool dns set example.com www A 1.2.3.4 --dry-run --jsonExit codes: 0 success Β· 1 error Β· 2 reserved for warnings/attention (e.g. future health)
--dry-run: supported on mutating DNS (dns set, dns delete). JSON mode skips interactive confirmation.
Where secrets live:
- Secrets are encrypted with AES-256-GCM at
~/.config/indietool/secrets/ - The encryption key is stored in your OS keyring (default) or as an age-encrypted file (
~/.config/indietool/keys/) - No cloud, no sync, no telemetry β everything stays on your machine
Threat model:
indietoolnever phones home. Zero telemetry.- Secrets are useless without your encryption key (OS keyring or SSH private key)
- If you lose your machine, secrets are unrecoverable (by design)
- For cross-host access, use
age-sshbackend + SSH agent forwarding
Provider tokens:
- API keys for Cloudflare/Porkbun/etc. are stored in
~/.config/indietool/config.yaml - File permissions are restricted to your user (
chmod 600) - Consider using environment variables or
indietool secretsfor sensitive tokens in shared environments
| Provider | Domains | DNS | Secrets |
|---|---|---|---|
| Cloudflare | β | β | β |
| Porkbun | β | β | β |
| Namecheap | β | β | β |
| GoDaddy | β | π§ | β |
| The Little Host | β | β | β |
| Local | β | β | β |
Legend:
- β Full support
- π§ In development (GoDaddy DNS coming soon)
- β Not supported
Notes:
- Domains: Domain registration management, expiry tracking, nameserver updates
- Cloudflare Registrar (beta): buy domains via API (
domain check/domain register) and manage auto-renew (domains renew,domain get,domain set) through the new Registrar API; privacy/lock remain dashboard-only until the API supports them
Sandbox testing: point the Cloudflare provider at the Registrar Sandbox API (test environment, no billing) with "indietool config add provider cloudflare --sandbox" (or "sandbox: true" in the provider config). The sandbox mirrors the production Registrar API under /registrar-sandbox/... and supports only com/net; purchases are free but persist. It requires an API token with Registrar Sandbox permissions and full contact data on register (no Express Mode).
- DNS: DNS record management (list, create, update, delete) with ID-based targeting
- Secrets: Local encrypted secret storage (OS keyring or age-ssh backend)
Encrypted locally at ~/.config/indietool/secrets/. The encryption key is stored in your OS keyring (default) or as an age-encrypted file at ~/.config/indietool/keys/ when using the age-ssh backend.
Secrets are useless without your encryption key. With the default keyring backend, start fresh on the new machine. With the age-ssh backend, your key file (~/.config/indietool/keys/) and SSH private key are both required β back up the keys directory if you need portability.
Experimental. Windows binaries are available in releases, but testing is limited. macOS and Linux are fully supported.
If you're on Windows and hit issues, please open an issue β we want to make it work!
- Ensure your keyring (Keychain or gnome-keyring) is unlocked
- Check file permissions on
~/.config/indietool/secrets/
GUI keyrings like GNOME Keyring require a graphical session to unlock, so they fail over SSH. Use the age-ssh backend instead:
indietool secrets init --backend age-sshThis encrypts the database key with your SSH public key. To decrypt over SSH, connect with agent forwarding enabled:
ssh -A yourserver.example.com
# or add 'ForwardAgent yes' to your ~/.ssh/config- Check file permissions on
~/.config/indietool - Ensure your user has write access to the config directory
- Double check key/secret pair
- Some registrars require IP allowlisting or scopes
- π§© Registrar support: Cloudflare, Porkbun, Namecheap, GoDaddy
- βοΈ DNS management: GoDaddy implementation in progress
- π» CLI only β no web UI or GUI planned
- π Secrets not synced across machines (by design β use age-ssh for cross-host access via SSH agent forwarding)
- πͺ Windows support is experimental
- π indietool.dev
- π¦ GitHub Releases
- π Report issues
- π¬ Discussions & roadmap