DEV Community: Xu Bian

How much does a personal independent site really cost?

Xu Bian — Sun, 03 May 2026 23:13:20 +0000

The Short Version

A personal independent site can start at $0/year.

If you do not buy a top-level domain, you can publish the first version on a free provider subdomain from Cloudflare Pages, Netlify, Vercel, or GitHub Pages. An address like your-name.pages.dev is already enough for learning, drafts, a small portfolio, or a family project.

That does not mean a site stays free forever. Costs usually appear when:

You want a domain that belongs to you.
You use paid tools such as Codex, ChatGPT, design software, or image generation to move faster.
Your site grows into heavy media, email, databases, login, comments, search, or commercial features.

So the real question is not “can I hack together the cheapest possible site?” The better question is: where does a normal person actually spend money when building a serious personal site?

Separate Three Kinds Of Cost

When people ask what a website costs, they often mix three different bills.

Infrastructure cost keeps the site online: domain, DNS, static hosting, storage, CDN, and certificates.

Tool cost helps you build faster: Codex, ChatGPT, design tools, image generation, writing tools, and code editors.

Maintenance cost keeps the site useful over time: new content, privacy review, backups, redesigns, renewals, and broken-link cleanup.

For a static personal site, the first category is often the cheapest one. The expensive part is attention, plus any tools you buy to save time.

Three Budget Routes

Route One: Start Free

Budget: $0/year

Best for:

Learning before you know whether you will keep publishing.
Giving projects, notes, or family material a temporary public address.
Accepting a provider subdomain.
Avoiding business email, backends, memberships, payments, and databases.

A free first version can look like this:

Item	Choice	Estimate
Domain	Use `.pages.dev`, `.netlify.app`, `*.vercel.app`, or GitHub Pages	$0
Static hosting	Cloudflare Pages, Netlify, Vercel, or GitHub Pages free tiers	$0
HTTPS	Automatic on the platform	$0
Content	Markdown, MDX, and ordinary image files	$0
Email	Keep using Gmail or public social profiles	$0
Analytics	Cloudflare Web Analytics or GA	$0

The tradeoff is ownership of the address. If you move providers later, the old provider subdomain may stop being the stable entrance to your work.

For version one, that is fine. If you do not yet know whether you can keep the site alive for a month, not buying a domain is a reasonable decision.

Route Two: Own The Address

Budget: about $10-20/year for basic infrastructure

Best for:

Treating the site as a long-term public identity.
Putting the URL on a resume, portfolio, social profile, or business card.
Wanting readers and search engines to remember your domain instead of a platform subdomain.

This route usually adds only one paid item: a domain.

Item	Choice	Estimate
Domain	Buy a `.com`, `.net`, `.dev`, or similar top-level domain	Often about $10-20/year, depending on TLD and registrar
DNS	Cloudflare DNS or registrar DNS	$0
Static hosting	Cloudflare Pages, GitHub Pages, Netlify, or Vercel free tier	$0
HTTPS	Automatic on the platform	$0
Inbound email	Cloudflare Email Routing into Gmail	$0
Outbound email	Start with Gmail, upgrade later if needed	$0+

As of May 3, 2026, Porkbun's domain pricing page shows .COM from $11.08, but domain prices vary by TLD, first-year promotion, and renewal. Always check the renewal price before buying. Cloudflare Registrar says it sells and renews domains at cost without markup, but you still pay registry and ICANN costs.

This is the route I would recommend for most serious first versions: buy the domain, keep hosting free, and keep the content as files you control.

Route Three: Add Tools And Growth

Budget: $20/month and up, depending on what you add

Best for:

People who already know they will publish regularly.
People who want AI tools to reduce the technical and writing burden.
Sites with large images, videos, downloads, or interactive features.
Sites that need professional email, collaboration, a CMS, database, search, comments, or automation.

At this point the cost is less about “the website” and more about the workbench around it.

Item	When it matters	Estimate
Codex / ChatGPT	You want AI help editing code, writing pages, running checks, and organizing content	ChatGPT Plus is listed at $20/month; Codex limits and rates depend on plan and usage
Object storage	Images, attachments, or downloads outgrow the repo	Cloudflare R2 has a free Standard storage allowance, then charges by storage and operations
Professional email	You need to send as `hello@yourdomain.com`	Free forwarding can start it; full sending usually needs a mail service
Paid hosting	You need higher build limits, teams, serverless functions, or commercial features	Free to monthly plans, depending on provider
Database / CMS	You need login, comments, memberships, forms, or non-technical editing	Can start free, then becomes usage-based
Paid analytics	You need privacy-focused analytics, team reports, or longer retention	Free to monthly plans

This is not the route for day one. Ship the site first, learn whether you will maintain it, then upgrade.

Is Codex A Website Cost?

Yes, but only if you count it correctly.

If you already pay for ChatGPT Plus, Pro, or a team plan, using Codex for your site may be a near-zero marginal cost. It is another use of a tool you already have.

If you subscribe to ChatGPT Plus only to build the site, then you can count it as a $20/month tool cost. It is not hosting, and it is not a domain bill. You are paying to save time, lower the technical barrier, and let an AI assistant inspect and edit the project.

OpenAI's help docs say Codex is included with ChatGPT Plus, Pro, Business, and Enterprise/Edu plans, while usage limits depend on the plan and task complexity. The Codex rate card moved toward token-based credit usage in April 2026, so “$20/month” should not be read as an unlimited Codex promise.

A more practical calculation:

If you only use AI to build version one:
Domain $10-20/year + AI tool $20/month, then cancel when done if you want.

If you use AI all year for writing, site edits, images, and content operations:
Domain $10-20/year + AI tool from $240/year.

Codex is an efficiency cost. It is not a required infrastructure cost.

Do You Need A Domain?

No.

Without a domain, you can use provider subdomains:

Cloudflare Pages: your-site.pages.dev
Netlify: your-site.netlify.app
Vercel: your-site.vercel.app
GitHub Pages: username.github.io

Those addresses open, share, and work. For learning, experiments, temporary portfolios, and family projects, they are enough.

The reason to buy a domain is not status. It is durability:

You want readers to remember one stable address.
You may change hosting providers later without changing public links.
You want to put the URL on a resume, portfolio, card, or long-term profile.
You want search engines to associate your name and work with your own address.
You want an address such as hello@yourdomain.com.

My rule for beginners: if you have not published three pieces or maintained the site for four weeks, wait before buying the domain. Prove the habit first.

Why Can Static Hosting Be Free?

Because static sites are cheap to serve.

A static site is mostly HTML, CSS, JavaScript, and image files. When someone opens a page, the platform sends files from a CDN. It does not need to run a custom server program for every request.

Cloudflare Pages advertises unlimited static requests. Its limits documentation lists 500 builds per month on the Free plan, 100 custom domains per project, and up to 20,000 files per Free-plan site. Netlify's pricing page lists a Free plan at $0 with 300 credits per month. Vercel documents the Hobby plan as free with automatic HTTPS, Git integrations, preview deployments, and 100 GB of Fast Data Transfer. GitHub Pages describes itself as static hosting for HTML, CSS, and JavaScript files from a repository.

That is why a first personal site should avoid unnecessary backend complexity. The closer it stays to static files, the cheaper and easier it is to move.

Will Images, Video, And Downloads Become Expensive?

Normal images usually will not.

A few compressed images in each article can live in the repository or static hosting. Costs become more likely when you publish:

Many full-resolution images.
Video files.
Large PDFs, software packages, audio, or downloads.
A frequently accessed asset library.

Then object storage may make sense. Cloudflare R2's pricing page lists a 10 GB-month monthly free allowance for Standard storage, then storage and operation charges after that, with no Internet egress bandwidth fees. That is generous for ordinary personal sites, but heavy reads can still create operation costs.

For version one, keep it simple: compress images, host video on YouTube, Bilibili, or another video platform, and embed or link from the site.

Do You Need Paid Email?

Not for version one.

You can start with Gmail, social links, or a simple contact page. After buying a domain, you can think about hello@yourdomain.com.

If you only need inbound mail, Cloudflare Email Routing says it can create custom addresses and route them to your preferred inbox, and it is free and private by design. That solves receiving and forwarding. It is not a full professional mailbox. Reliable sending from your domain usually needs Google Workspace, Fastmail, Zoho, iCloud Custom Email Domain, or another mail service.

For a personal site, solve “can people reach me?” before solving email branding.

When Do You Need A Backend, Database, Or CMS?

When the need is real.

Version one usually does not need a database. Articles, projects, and pages can be Markdown or MDX files.

Backend costs start to make sense when:

Users need to log in.
Readers can comment.
You have paid content or memberships.
Forms need a real admin workflow.
Non-technical collaborators need to edit content.
Search, recommendation, or personalization becomes complex.

All of that can be built later. None of it is required for a first independent site.

A More Realistic Budget Table

Scenario	First-year infrastructure	AI / tools	What it feels like
Learn and test	$0	$0+	You can start now
Free subdomain + one month of Codex	$0	about $20	Cheapest serious validation route
Domain + free static hosting	about $10-20	$0+	Best serious starting point
Domain + year-round ChatGPT Plus / Codex use	about $10-20	about $240/year+	Tool cost, not hosting cost
Growing personal site	about $10-20+	$20-50/month or more	Depends on email, storage, CMS, analytics, and backend

The most common mistake is to say “an AI-built site costs hundreds per year.” More precise: the site itself can cost about ten to twenty dollars per year; separately, you may buy an AI tool that helps with coding, writing, images, and operations.

My Recommendation

If you do not have a site yet:

Start on a free subdomain and publish version one.
Publish three pieces, or maintain the site for four weeks.
If the habit survives, buy a domain.
Upgrade storage, email, backend, or team features only when they block real work.
Judge Codex and similar AI tools by time saved, not by whether they are required.

The best thing about an independent site is that it does not require a large commitment on day one. Start at $0, prove that you want to keep writing and organizing your work, then spend money where the need is real.

References

Originally published on my personal site:
https://marlinbian-site.pages.dev/en/tutorials/personal-site-cost/

More links: GitHub · YouTube · LinkedIn · Bluesky · Mastodon · Discord

Build your own independent site with Codex

Xu Bian — Sun, 03 May 2026 12:37:44 +0000

The Short Version

You do not need to become a programmer before you can have your own place on the web. You need to make three decisions first:

What should last: artwork, essays, projects, learning notes, tutorials, or a family archive.
How often you will update it: weekly, monthly, or only when a real project is ready.
How much maintenance you can accept: no-code, light file editing, or a long-term code project.

Codex sits between light file editing and a long-term code project. It is not a magic website button. It is a local collaborator that can inspect a project, edit files, run checks, and explain the changes. The official OpenAI Codex CLI documentation describes it as a coding agent you can run locally from the terminal, working inside the selected directory.

That makes it useful for the repetitive parts: setting up folders, creating pages, adjusting styles, turning Markdown into pages, running builds, and checking that private material has not entered the public site.

A Website Is Not Just Another Feed

Social platforms are useful. They are where distribution, feedback, and discovery happen. But they are not good archives. Rules change, timelines bury work, and links can become fragile.

An independent site solves a different problem: it gives your public work a stable address.

A healthier publishing order looks like this:

Publish the complete version on your site first.
Then adapt it for Xiaohongshu, WeChat, YouTube, Bluesky, DEV.to, or other platforms.

This keeps the source version in your hands. You can still benefit from social platforms without letting them become the only copy of your work.

Choose By Person, Not By Tool

Designers And Artists

Start with a portfolio. Do not start with a complex blog system.

Your strongest assets are images, project process, taste, and judgment. A first version can be very small:

Home: one clear sentence about who you are, plus selected work.
Work pages: one page per project, with images, context, process, and outcome.
About: what you do, what kind of collaboration fits, and how to contact you.

For a designer, Codex should not decide which work is good. Its job is to make the structure steady: create pages, keep image sizing consistent, add alt text, update navigation, and run checks.

Engineers And STEM Builders

Start with project records and reusable notes.

It is easy to over-engineer your own site. The better first version is practical:

Project pages: what you built, why it exists, what stack you used, and what happened.
Tutorials: reusable explanations for things you keep teaching.
Playgrounds: small demos or tools people can try without an account.

If you are comfortable with Git, Markdown, Astro, and static hosting, Codex can be very effective. It can work inside the repository and run the build. Your job is to review the changes and keep the important decisions explicit.

Children And Family Projects

Start with safety, simplicity, and adult review.

A child's site should not begin with public attention. A better goal is a safe record:

A small wall of work: drawings, crafts, Scratch projects, or reading notes.
A learning log: one or two sentences each week.
A review flow: drafts stay local until an adult checks them.

Privacy matters more than polish. Do not publish school names, home locations, routine schedules, identity documents, or anything that makes the child easy to identify. Codex can help scan text, but an adult must make the final decision.

Writers, Teachers, And Small Service Businesses

Start with articles and useful resources.

Writers need durable long-form links. Teachers need organized materials. Small service businesses need a clear public introduction. A first version can be:

Home: what value you provide.
Writing or resources: public material grouped by topic.
Contact: one low-friction way to reach you.

You do not need a complex system at the beginning. Let the work have stable URLs first. Add newsletters, courses, payments, membership, or automation only when the content proves the need.

The Steady Route

If you do not know what to choose, I would start here:

Write content in Markdown or MDX.
Build the site with Astro.
Keep history in Git.
Deploy to Cloudflare Pages, GitHub Pages, Netlify, or Vercel.
Treat social platforms as distribution, not the archive.

This route is not the only good route. Its advantage is durability. Your content remains ordinary files. If you change themes, hosting providers, or domains, the articles and images are still yours.

No-code tools are also valid. Framer, Webflow, Carrd, Notion-style sites, and similar tools can be faster for a single polished homepage. The deciding question is simple: if you need one beautiful page, no-code may be faster. If you want years of essays, tutorials, projects, and interactive demos, a file-based site is usually steadier.

A Better First Prompt For Codex

This prompt is too vague:

Build me a personal website.

A better starting prompt is:

Please help me build a personal independent site in the current directory.
The audience is not programmers only. People should understand me through work and writing.
The first version needs a home page, about page, writing list, project list, and contact page.
Store content in Markdown or MDX. Public content should not depend on a database.
Inspect the project structure first, give me a short plan, and wait before editing files.

If you already have materials, add a privacy boundary:

The materials/inbox folder contains images and drafts.
First list what is suitable for public use and what may be private.
Do not move anything from private into public or src/content.

A good prompt does not lock every technical detail. It states the goal, audience, boundaries, and acceptance checks.

Keep Version One Small

The first version only needs five areas:

Home: one clear positioning sentence and recent work.
About: who you are and what you are focused on now.
Writing: articles and durable opinions.
Projects: work, experiments, and tools.
Contact: email, social links, and collaboration paths.

Avoid login, comments, CMS complexity, memberships, heavy animation, and multilingual admin systems at the beginning. Add them only after you have a real publishing rhythm.

Launch Checklist

Check at least these items before publishing:

Every page is readable on a phone.
The home page explains who you are within ten seconds.
Each article has a title, description, date, and tags.
Images have reasonable dimensions and alt text.
Secrets, private drafts, backend screenshots, and child-sensitive details are not in public folders.
The build command passes.
Important links open correctly.

This is where Codex helps: run the build, inspect diffs, and list risks. Still, read the public pages yourself before shipping.

References

Originally published on my personal site:
https://marlinbian-site.pages.dev/en/tutorials/build-personal-site-with-codex/

More links: GitHub · YouTube · LinkedIn · Bluesky · Mastodon · Discord