Rules
One bad pod can get all of podu.dev blocked by browsers, which breaks everyone's pod. So these rules are short, and we enforce them.
What's not allowed
- Phishing and fake logins. Anything that collects passwords or payment details under false pretences.
- Malware. Serving or linking to harmful downloads.
- Impersonation. Pretending to be a company, brand or person you aren't.
- Spam and scams. Including crypto giveaways and illegal content.
- URL shorteners. No redirect farms or link shorteners.
- Reselling. Pods aren't for sale or rent.
Limits
These are the limits the service enforces.
| What | Limit |
|---|---|
| Pods per GitHub account | 5 by default. We can set a personal limit for an account. |
| GitHub account age | At least 30 days old. |
| Pod changes | 10 per hour: claims, edits and deletes together. |
| Pointing at a host (CNAME) | One host name. A CNAME is the only record on its name. |
| Pointing at your server (A) | One or 2 public IPv4 addresses. No IPv6. |
| TXT on the pod name | Up to 5 values, on pods that point at your own server (A records) only. |
| TXT names | Up to 3 per pod. Each starts with an underscore, like _atproto, and is at most 63 characters. _dmarc and DKIM names come only through email authentication. |
| TXT values | Up to 2048 printable ASCII characters each, and 4000 characters for all values on one name. |
| Email authentication | SPF, DMARC and up to 3 DKIM selectors, only while the pod has approved email (MX). Removing email removes them. |
| Vercel verification | Up to 2 values per pod at _vercel.podu.dev, removed after 14 days. Up to 10 changes per hour. |
| Other names | No other sub-names and no wildcards: www, mail or * under your pod can’t be added. |
| Email (MX) | Up to 5 mail servers, on request, on pods with A records only. |
| Own nameservers (NS) | 2 to 6 nameservers, on request. They replace all other records. |
| Request reason | 10 to 500 characters. |
| Email provider name | 2 to 60 characters, on an email request. |
| Open requests | One per pod at a time, and up to 3 open name requests per account. |
Email and nameserver requests
Email (MX) records and your own nameservers (NS) are added only on request, from My Pods. A person at Podu checks every request by hand. Requests are approved unless the pod name is tied to a well-known brand or trademark. Your pod keeps its records while you wait, and we email you the decision, with a note when there is one.
Own nameservers (NS)
What we accept
- You own the pod, and it is not taken down or being deleted.
- 2 to 6 different nameservers, each a host name that resolves, none at or under podu.dev.
- A reason of 10 to 500 characters: a short note on what the pod is for, which helps the reviewer.
- One open request per pod. A pod that already has its own nameservers can ask for different ones.
What we refuse
- Nameservers that do not resolve, are IP addresses, or sit at or under podu.dev. These are refused as you send the request.
- A banned account, or a pod that is taken down.
- A pod name tied to a well-known brand or trademark (for example Microsoft, Google or GitHub). A person checks this by hand.
Once approved, it stays while you keep the pod, unless the pod is taken down under the Acceptable Use Policy. NS replaces all other records on the pod and you answer for everything under it. Switch back to normal records any time with Change target in My Pods, unless the pod is taken down or being deleted. Different nameservers need a new request. See the own nameservers guide.
Email (MX)
What we accept
- You own the pod, it points at your own server with A records, and it is not taken down or being deleted.
- Up to 5 different mail servers, each a host name (not an IP address) outside podu.dev, with a priority.
- The name of your email provider (2 to 60 characters) and a reason of 10 to 500 characters: a short note on what the mail is for, which helps the reviewer.
- One open request per pod. A pod that already has email can ask for different mail servers.
What we refuse
- A pod that uses a CNAME. DNS does not allow MX next to a CNAME, so point the pod at A records first.
- Mail servers that are IP addresses or podu.dev names. These are refused as you send the request.
- A banned account, or a pod that is taken down.
- A pod name tied to a well-known brand or trademark (for example Microsoft, Google or GitHub). A person checks this by hand.
Once approved, it stays while you keep the pod, unless the pod is taken down under the Acceptable Use Policy. The MX records sit next to the pod’s A records, and you can add SPF, DMARC and DKIM records for them. You can remove them yourself in My Pods at any time, unless the pod is taken down or being deleted, and that needs no approval. Removing email also removes its SPF, DMARC and DKIM records. Send-only mail services (like Amazon SES) need these records too, so request email first even if you only send mail. See the ImprovMX guide.
Official podu.dev names
- www.podu.dev
- dash.podu.dev
- podu.dev
The only websites Podu runs are www.podu.dev, dash.podu.dev, where you sign in and manage your pods, and podu.dev, which redirects to www.podu.dev. Apart from a few technical names that Podu keeps for its own email and services and for domain checks (like _psl, and _vercel, where users publish their own host checks), every other name under podu.dev is a pod run by one of our users, not by us. Podu never asks for your password or payment details on a pod. If a pod pretends to be Podu, report it.
Policies
Terms of Service
Podu is free and comes as is, with no uptime promise. You need to be 16 or older with a GitHub account at least 30 days old. You can hold 5 pods by default. Email and own nameservers are on request, checked by a person, and approved unless the pod name is tied to a well-known brand or trademark. Pods that stop working are warned, then released.
Privacy Policy
Your pod's name, where it points and your GitHub username are public. We keep little else, delete logs, closed reports and decided requests after 30 days, and use only sign-in cookies plus reCAPTCHA on forms. You can delete your account yourself.
Abuse, takedowns and appeals
Report a pod with the form or by email. A person reviews every report. Owners are told why a pod came down and can appeal within 30 days.
Security policy
Found a security problem in Podu? Email security@podu.dev. Good-faith research that follows the rules is welcome.
Open source & transparency
Podu is free and open by design.
- No ads, no tracking, no analytics.
- We don't sell data, and there are no paid tiers.
- Every pod is a public record in podu-dev/register.
- Takedown and release counts are published there every month.
- The code is MIT licensed on GitHub at podu-dev/app, public from launch day.
- The policies are licensed under CC BY 4.0. Reuse them, with credit.
Report abuse
Reports go through their own form. How takedowns and appeals work is on the abuse page.