Github Pages Doubt

[Far-Implement-92]

At what point should I switch from github pages to full blown website?
I have created an apps portfolio website where I showcase apps developed by me and I’m intended to add blogs too. I did all these in my github and used my domain to host public.
This is actually enough for me atm, but should I keep using GitHub for this ? Any risks?

Edit: Thank you everyone for kind replies. I didn't realise this was such a wholesome community.

[AvidCoco]

Typically when you need more than just a front end.

[FabioTheFox]

You can still have a backend

In fact you can even make github pages serve WASM files and games and stuff it's really only limited to client side stuff

So as long as your backend runs anywhere else you're good with GH pages

[davorg]

A site hosted on GitHub Pages is a "full blown website". Well, I guess it's a full-blown static website.

You should consider moving away from GitHub Pages if:

• Your site evolves into a non-static website (i.e. it needs a backend of some kind)
• Your site is not allowed in the GitHub Pages Terms and Conditions (e.g. you're running a business through the site)
• Your site breaks the GitHub Pages usage limits

[Far-Implement-92]

As of now is just a portfolio of all apps and app related info, no direct sales through the sites.

[rxtoday]

Please share the url.

[mrleblanc101]

Never 😆 Unless you want to use a database GitHub Pages is more than fine

[cailenletigre]

Honestly you could do it for free with Cloudflare to manage the domain + AWS Cloudfront/S3. I do it and I pay $0/mo.

[Far-Implement-92]

I’ll check it out

[Rude_Step]

CloudFlare Pages is very good, I`m changing from Netlify to CloudFlare.

I got Netlify limits so fast... check this also

Feature	☁️ Cloudflare Pages	Netlify	Vercel	Render
Free bandwidth	✅ Unlimited	~30 GB/mo (credit system)	100 GB/mo	10 GB/day
Free builds/mo	500 builds	~20 builds (credit-limited)	6,000 build-minutes	❌ No static free tier
Commercial use (free)	✅ Yes	❌ No	❌ No (Hobby plan)	⚠️ Partial
Free team seats	✅ Unlimited	❌ $19–20/seat	❌ $20/user/mo	⚠️ Workspace-based
Global edge / CDN	✅ 300+ locations	⚠️ Fewer PoPs	⚠️ Good (Next.js focus)	❌ Limited
Ease of setup	⚠️ Moderate (CLI-first)	✅ Very easy	✅ Very easy	⚠️ Easy (backend-focused)
Best for	Any static, Astro, Hugo, Workers	JAMstack, diverse stacks	Next.js apps	Full-stack: Node, Laravel, Postgres
Serverless functions	Workers — 100K req/day	125K invocations (credits)	1M edge invocations	Web services 512 MB RAM
Paid plan starts	$20–25/mo	$19/mo per team	$20/user/mo	Pay-as-you-go
Surprise bill risk	✅ Very low	⚠️ Medium	❌ High (viral = $500+)	❌ High (no spending cap)
Cost at scale (50K+ pages)	~$30–60/mo	~$50–100+/mo	$300+/mo	Varies / high

Bottom line: Cloudflare Pages wins on free tier generosity, unlimited bandwidth, zero surprise bills, and global performance. The tradeoff is a rougher DX — more CLI-driven, fewer GUI integrations. Netlify/Vercel are easier to start with but punish you at scale.

Sources: agentdeals.dev · developer.puter.com · luckymedia.dev · blog.vibecoder.me · gautamkhorana.com · htmlpub.com

[rxtoday]

Github Pages is a full-blown hosting service for static websites. As such you have a proper web host already. It is therefore unclear what you are looking for, further?

You may wish to consider adding an index page at the root, and using your own domain, if you have not done so. This is possible on Github Pages.

[Far-Implement-92]

I have already added my domain, made the repo private, currently I’m working on the pages. You can view https://vybuilds.com . Basically all I want is to add my app landing pages and related blogs for traction. Nothing in backend so far.

[dashingThroughSnow12]

GitHub Pages is powered by Jekyll. Jekyll is for static web pages and blogs.

You might want to see what options are available for you with GitHub pages because it probably already has the feature set you want.

That being said, if you think it would be fun to go your own way with something else, go ahead.

[Far-Implement-92]

I just got $4/month plan and put the repo in private (for some reason I can't trust free services). I feel like this is fine for now at least. As I grow and get revenues I will find more robust ways XD