register-domain.md |
turn a project idea into a registered .ro domain hosted on ird DNS with the first records in place — checking availability, price and balance before it spends anything. |
bring-domain-dns.md |
move the DNS hosting of a domain you already own elsewhere (.com, .eu, .dev, anything but .ro) onto ird nameservers without downtime: copy the live records first, hand you the exact nameservers to set at your registrar, then confirm the switch and the seeded zone. |
dns-records.md |
bring a zone hosted on ird DNS to a desired record set — web endpoints, mail (MX, SPF, DKIM, DMARC), service verification TXTs, CAA — as a reviewed plan applied without collateral changes. |
brand-protection-domains.md |
turn a brand name into look-alike .ro candidates — typos, plurals, hyphenations, diacritics-stripped spellings and the second-level .ro forms (com.ro and friends, where the availability check accepts them) — check them in bulk, price the shortlist, register only the ones you confirm, park each on ird DNS pointing at the main site, and leave auto-renew on. |
delegated-domain-management.md |
work on domains that other ird accounts delegated to you — an agency running client domains, a contractor with scoped access — and stay inside the granted scopes and the billing arrangement: it reads every share first, does each client's checklist, and ends with a monthly report of what it did on whose credits. |
dns-snapshot-diff.md |
take a copy of a domain's live DNS — yours, a client's, one hosted anywhere — save it as JSON, diff it against an earlier snapshot or against the zone ird hosts, add the registry and whois facts, and produce a drift report or a migration-readiness report. A snapshot can also become the seed of a DNS claim, so nothing is lost on the switch. |
dnssec-enable.md |
sign a .ro domain the right way for where its zone lives: on ird DNS it is one switch (ird dns dnssec), on your own or another host's nameservers it means publishing the DS records at the .ro registry yourself — then prove validation with dig and delv, keep the one ordering rule that stops a signed domain from going dark, and have the rollback ready. |
domain-renewals.md |
list every domain on the account that expires within a window — with its auto-renew flag and the price of extending it — check the balance, renew only the ones you confirm, set auto-renew the way you want it, and prove the new expiry dates. |
domain-transfer-in.md |
bring a .ro domain you hold at another registrar onto ird as its registrar — using the authorization key the old registrar gives you — then host its DNS on ird with the live records copied before the nameservers change, so nothing goes dark, and verify the result. Only .ro is transferred: any other TLD is claimed onto ird DNS instead (the bring-domain-dns prompt). |
domain-transfer-out-or-trade.md |
move a .ro domain registered at ird to another registrar, or hand it to a new holder (a registry "trade"), without the site or mail going dark: it verifies the registrant email if the registry needs it, snapshots the zone first, sends the one registry request after showing you exactly what the CLI charges and says, follows the request, and takes the ird zone down only once the new host resolves. |
email-dns.md |
wire a zone hosted on ird DNS to a mail provider — Google Workspace, Microsoft 365, Fastmail, Proton Mail, or values you paste — with the provider's MX, SPF, DKIM, verification record and client autodiscovery, plus a DMARC policy rolled out in stages. It reads the zone first, merges TXT sets instead of clobbering them, and proves each record with dig before the MX cutover. |
leave-ird-dns.md |
take a zone ird hosts — a .ro registered here, or a domain from another registrar brought in with a claim — to another DNS host cleanly: export every record, rebuild and verify the zone at the new host, switch the delegation, confirm the domain answers from there, and only then release the claim or disable the zone, checking that the hourly zone fee actually stops. |
own-nameservers-glue.md |
delegate a .ro domain registered at ird to nameservers you run yourself under that same domain (ns1.example.ro, ns2.example.ro): the glue records at the registry, the delegation change, the dig +trace proof that the world reaches your servers, what to do with the ird-hosted zone afterwards, and the way back if it goes wrong. |
static-site-ipfs.md |
put a folder of static files (a built site, docs, a landing page) online at https:// on the ird IPFS gateway — with a stable IPNS name, so updates are a re-publish, never a DNS change — and keep the pin lifecycle tidy so you pay for one copy. |
share-files-ipfs.md |
pin a file or folder on the ird IPFS gateway and hand you a link to share — optionally encrypted on your machine first so the network only ever holds ciphertext — and take it down again when it has served its purpose. |
expose-local-app.md |
expose something running on your machine (a dev server, a demo, a webhook receiver, a home service) at https:// through an ird HTTPS tunnel — DNS and TLS handled — with a proper offline page and a clean teardown so you don't keep paying for a demo you finished. |
publish-repos.md |
publish git repos as anonymous, publicly clonable repos at https:///.git — static files on IPFS, no git server — with the anonymity gates, pin lifecycle and end-to-end verification that the ird.cod-sursa.ro ecosystem itself uses. |
branch-preview-sites.md |
give every branch or pull request of a static site its own preview at https://.preview.example.ro on the ird IPFS gateway — one IPNS name per preview, re-published on each build — then audit what previews exist, what they cost, and tear down the ones whose branches are merged. |
ci-publish-site.md |
wire your CI pipeline (GitHub Actions or GitLab CI) to publish a static site to the ird IPFS gateway on every push: an API key kept in the CI secret store, the ird CLI run non-interactively, the build pinned, the IPNS name re-pointed, the previous root unpinned, and the job failing loudly on any error — with a working YAML snippet. |
encrypted-backups-ipfs.md |
turn a folder or database dump into dated, encrypted backups pinned on the ird IPFS gateway — encrypted on your machine to your own key (or a password), so the network only ever holds ciphertext — keep the last N, unpin the rest, and prove at least once that a restore actually decrypts to the same bytes. |
ipfs-asset-cdn.md |
serve your build's static assets (CSS, JS, fonts, images) from https:// on the ird IPFS gateway, unbranded — every build a new immutable root, filenames versioned so browsers can cache forever, old roots retired on a schedule you set — and tell you what it costs to store and serve. |
mirror-existing-ipfs-content.md |
keep content that already lives on IPFS alive on the ird gateway: given a CID, estimate size and cost, pin it (ird fetches it from the network), hand you a gateway URL, optionally serve it unbranded at your own hostname, verify the bytes actually arrived, and unpin it when it has served its purpose. |
vps-server.md |
create an ird VPS (EU, billed hourly from credits), anchor it at a hostname on your domain, and run a sensible first-boot hardening — updates, firewall, non-root user, optional Docker — with the cost stated before anything is created. |
one-click-app.md |
deploy an app from the ird catalog on a dedicated server at . — DNS and TLS automatic — handle the one-time root password correctly, wait for it to come up, and know how to remove it. |
deploy-app-on-vps.md |
put a Docker Compose app on an ird VPS behind Caddy — TLS issued automatically, the hostname's A record set on your ird zone, secrets copied out of band — with a repeatable redeploy that keeps the proxy up, a snapshot before every risky upgrade, and the logs to prove it works. |
vps-handover.md |
prepare an ird server (or volume, or snapshot image) for handover to another account — secrets rotated, your keys removed, a snapshot in hand — walk you through the offer in the ird panel, watch the transfer until it is accepted, and verify what changed on both sides. Works in reverse for receiving one. |
vps-incident-response.md |
work an incident on an ird VPS the way an operator would: tell a pending provider job from a hung box, climb the power ladder gently (graceful shutdown before a hard reset), snapshot before anything destructive, fall back to the account panel when SSH is gone, check the hostname still points at the server, rotate a leaked SSH key, and hand ird a ticket with real diagnostics when the fault is on their side. |
vps-snapshot-restore.md |
run the backup lifecycle of an ird VPS: take and list snapshots, rebuild a server from one (that's also how you resize — a new server on a bigger tier from the snapshot), move the hostname over, attach a volume, retire old snapshots, and destroy the old server only after the new one is proven. |
vps-volume-data-disk.md |
put the data of an ird VPS — Docker volumes, a database, uploads — on a separate volume that outlives the server's own disk: create it, attach it at server create, format and mount it with an fstab entry, move the data over, and grow it later by moving to a bigger volume on a fresh server, deleting the old one only after the new one is proven. |
p2p-app.md |
create a p2p app on ird — WebSocket signaling, STUN/TURN, a libp2p circuit relay and an optional offline mailbox at .ap2p.ro or your own domain — lock it to your site's origins, test it end to end, and hand your codebase the exact client config. |
p2p-orbitdb-helia.md |
give a js-libp2p, Helia or OrbitDB browser app a dedicated circuit-relay-v2 peer on ird — peers reserve a slot on it, find each other over pubsub, upgrade to direct WebRTC, and, with the offline mailbox on, catch up on encrypted log entries and head CIDs even when no other replica is online. Limits sized, cost explained, tested with two browsers. |
p2p-production-hardening.md |
harden an existing ird p2p app for launch: tight origins, a branded wildcard hostname on your own zone, mailbox tokens minted only by your backend, limits sized to the rooms and peers you expect, monitoring hooks, a cost model from the relay rates, and a written rollback — each change snapshotted first and applied only on your yes. |
p2p-teardown-and-pause.md |
take a p2p app down in the right order — capture every setting into a JSON re-create recipe, stop new peers by tightening the origins, switch the relay off, drain and switch off the mailbox only with your explicit yes, detach the custom domains, delete the app, and prove the billing stopped — with the reverse path that rebuilds it from the recipe and tells your clients what changed. |
p2p-yjs-collab.md |
take a collaborative-editing app that already runs on y-webrtc, Trystero/WebTorrent or PeerJS and point it at an ird p2p app — the same hostname speaks all three signaling dialects, so the change is one URL in the client config, plus TURN so peers behind strict NATs still connect. Origins locked per environment, tested with two browsers, cost known. |
api-keys-automation.md |
set up ird API keys for unattended use — one key per job, named so you know what to revoke — wire them into scripts and CI with the right flags, prove each key works, and put a rotation and leak response routine in place, without the key ever landing in a repo or a prompt. |
directory-research.md |
mine the classified .ro web directory on ird — sites described, categorised, tagged, with language, sentiment and bias labels — for competitors, partners or link prospects around a topic, cross-check the interesting domains with registry and whois facts, test the name ideas the research throws up, and hand you a CSV you can work from. Directory labels stay labelled as the directory's; nobody's personal data is collected. |
ird-mcp-setup.md |
get the ird MCP server running for your AI tooling — the ird CLI installed and signed in, the server registered in your coding agent, editor or desktop client, the choice between your login session and an API key made deliberately — then prove it with free calls and tell you which jobs still need the CLI. No credential is ever pasted into the conversation. |
semantic-search-embeddings.md |
build a small semantic search / near-duplicate pipeline on ird jobs embed: your texts embedded once each, vectors cached on disk under a hash of the text so a rerun only pays for what changed, cosine ranking and duplicate pairs in a few lines of Python, the cost read from the price book before anything runs, and a mode that works unattended from a script with an API key. |
webhook-receiver.md |
give a local dev server a permanent public HTTPS address for Stripe, GitHub, Twilio or any other webhook sender — through an ird tunnel that survives reboots via the background agent — with signature verification wired in locally, a way to tell "the tunnel was down" from "my handler failed", and a teardown that actually stops the bill. |
account-audit.md |
go through everything on an ird account — credits, domains, DNS zones, IPFS pins and names, gateway domains, tunnels, servers, apps, p2p apps, shared domains, open tickets — and produce a monthly-cost table with concrete cleanup actions, applying only what you approve, line by line. |
plan-and-price-stack.md |
turn a list of resources you intend to run on ird — domains, DNS zones, IPFS storage and traffic, tunnels, servers, one-click apps, p2p apps, snapshots and volumes — into a monthly cost table from the live price book, compare two options, check your runway, and point out the cheaper way to get the same result. Nothing is created. |
spending-report-ledger.md |
turn the ird credits ledger into a month-by-month report — charges grouped per service, top-ups, refunds, adjustments and expiries on their own lines — reconciled against what is actually running on the account today, so charges for resources that no longer exist, credits about to expire and your remaining runway are visible. Nothing is changed — unlike account-audit (inventory plus approved cleanup) and plan-and-price-stack (pricing what you intend to run), this one only looks back. |
support-ticket.md |
turn "it doesn't work" into a ticket the ird team can act on: reproduce the problem, collect the right diagnostics with the CLI, redact anything secret, pick the service, keep it inside the size limits, submit it only after you read it, and follow the reply thread. Support is free per the price book. |