freehostingreviews.com

To add, after adding to docs,
https://pages.cloudflare.com/
https://youtu.be/mzNpuj4T66Q

let Claude do a review of one site, via Arena

And another
https://pico.sh/plus

https://www.freehosting.com/free-hosting.html – Looks promising, allows own domain. But ssl costs $5 one-time fee. No SSL — pointless with the browser security circus.

freehostingreviews.com

Sites that give info about free hosting are extremely popular.

ToDo: googiehost seems to allow your own domain on the free hosting – need to check this.

Try to track this one down too, it’s still working after some years, https://friendsvps.myfreesites.net/ -found it, see https://app.sitebuilder.com/auth/login — taken over by networksolutions and now is not free. Deleted it.

Here is a tor site offering free tor hosting, http://fhostingineiwjg6cppciac2bemu42nwsupvvisihnczinok362qfrqd.onion/

Reviews on Sites

I noticed when I was doing research into free hosting that more often than not my keywords brought me into someone’s review site. I had the idea to post reviews of all the different free web hosting sites on the actual sites themselves. I tried it but my design skills are pretty limited.

  • Each would link back to freehostingreviews.com with an eye-catching thing to see more free site reviews. Good SEO (though I care little about that mostly, in this case it would be useful).
  • Freehostingreviews.com will have a page with summaries of all free sites with links to each review. Perhaps a table layout.
  • We can frequent all the forums where people talk about free sites and low-end type subjects. These are extremly busy sites. Much of this would be done by the reviewers themselves anyway.

It seems crazy to review your competition, especially to do it fairly and honestly, but no matter what glowing reviews we give, we know that for most users satoshihost offers a far better deal.

My purpose in researching these sites was mostly for our friends in Africa and elsewhere who can’t afford web hosting, or perhaps can afford the likes of godaddy (spit!) and would be at least as well served with a free site. The free sites don’t offer the amazing deals that godaddy offers, but then neither does godaddy in reality, and our friends have better things to do with their money or time than get ripped off by corporate web sharks.

This means that we would be providing a good useful service to people who can benefit from it and at the same time attracting traffic from the exact audience we want to see our projects.

A general how-to section would be good too. For example, some of the free hosts have horrible page builders but they have a file manager so you can upload anything. How to get templates and modify them and then upload them – that kind of stuff.

Reviews

Done

In Progress

https://lovable.dev/projects/4c0d9bc8-6cf0-4a14-90cf-a786644e7d89. Published at freehostingreviews.lovable.app.

Reviewers

There are people who love doing reviews and people who would love a chance to show off their skills too – sure we could get volunteer reviewers, recruit from the forums, and pay them with free VPS or Web hosting.

Only the free sites that were consistent and usable are listed. Many sites have been tried and failed to work properly or had bad support, obtrusive ads, pop-ups or other tricks. These were deleted and will not be reviewed.

They can also be a portfolio to show the work of our web developers or reviewers, thus acting as an ad for them. We can put an ad (box) in the site linking to the web dev section of the main site. (probably on devsdirect.net)

  • Test out the support options and report on them
  • Use some of the features in the site itself
  • note especially any unique, rare or particularly well-implemented features
  • make a link to the uptime stats via uptimerobot.com from each site (example satoshihost) or use their api keys to embed something in the page.

These sites (and the overview page) can be advertised on forums etc.

Ads can be placed on any sites that allow it. (not google etc cos they suck)

Main questions to be answered in a box on the main review: (tick or ranking)

  • provider ads
  • own ads allowed
  • disk space
  • bandwidth
  • type of control panel
  • email

For each review there could be a box summarizing the main advantages of the free hosting plan, and maybe disadvantages too. The design of each site will be different, showing the best aspects of that host, but some things will be constant, e.g a Home page and pages for tools, service etc.

All sites contain a link back to the main review, with a brief, standard text description.

Resources

Some may be out of date now.
Here is a good list to go through: discourse.32bit.cafe

Free templates

might be useful for where there is ftp access.

Sitebuilders

Free Hosting

Free Reseller Hosting

Free “cloud” services (+ VPS)

our free instances are on the Servers page (not any more, they are not suitable except for people familiar with command line and even then their own systems (neccessary to be able to get command line access) are difficult to use.

  • https://www.oracle.com/ie/cloud/free/#always-free – e.g. 4 Arm-based Ampere A1 cores and 24 GB of memory usable as one VM or up to 4 VMs
  • IBM cloud – no root but also no card needed.
  • AWS is only for a year
  • Microsoft Azure is crap, only with student they do give a free vps but require ID.
  • MetalVPS is still offereng a free VPS (2023) see this forum thread. Seems like it’s pretty crap though and is only a shell account from which you can set up a VPS if you know how to from the command line.

Free Domain Names

  • eu.org gives free subdomains. Useful to try stuff out with. Our request (May 2023) for creation of domain NIMNO.EU.ORG has been accepted. Pointed it to a temporary site (via satoshihost direct admin) and after 13 months it’s still ok.
  • freedns.afraid.org has a choice of subdomains, the shortest being .us.to. Not tried it yet but seems ok.
  • freenom.com does free domains but really unreliable, could stop you any time with no reason given. [edit Apr 2023 – now is down more often than not]
  • getfreedomain.name is worth a look. Also lists some free hosting. -Not free, just ads for namecheap and other crap.
  • Also check out freename.io/ – they say free hosting too. -web3 and looks scammy. Not free.
  • https://freedomain.one/ – seems to work, using satoshihost.publicvm.com and satoshihost.work.gd
  • unstoppabledomains.com/ web3 domains only. Not free. SFT stuff (stupid tokens).

Dev Notes

The “Master Table”

or Feature Filter Idea

A filterable comparison system — is a fantastic way to help visitors quickly find a suitable host.
Instead of overwhelming them with giant tables, you could let them select priorities (checkboxes like “must support custom domains”, “must allow PHP”, “no ads”, etc.), and the site dynamically filters the list.

For bandwidth-constrained users, the goal should be:

  • Minimal data transfer (lightweight HTML + JS).
  • No client-side frameworks (avoid React/Vue).
  • Instant filtering without reloads.

So yes — a flat-file JSON approach makes perfect sense.

Why JSON (or even TXT) is Ideal

A JSON file per host, stored in something like /data/hosts/0001.json, might look like this:

{
  "name": "InfinityFree",
  "url": "https://infinityfree.net",
  "review_url": "https://infinityfree.freehostingreviews.com",
  "features": {
    "php": true,
    "mysql": true,
    "ssl": true,
    "ads": false,
    "ftp": true,
    "file_manager": true,
    "custom_domain": true,
    "storage_mb": 5000,
    "bandwidth_gb": "unlimited"
  },
  "notes": "No ads, free SSL, but no email accounts."
}

Then your main site just loads all /data/*.json files, builds the table, and filters them client-side (via a simple JavaScript function).
No backend, no database — just static hosting.

For users with limited data, you could even:

  • Lazy-load JSON only when filters change, or
  • Combine all entries into one compressed hosts.min.json (~a few KB even for 100+ hosts).

3. Filtering Logic

Example (pseudo-code in plain JS):

function filterHosts(requirements) {
  return hosts.filter(host => {
    return Object.keys(requirements).every(key =>
      host.features[key] === requirements[key]
    );
  });
}

You could build the form dynamically from a list of features — again, all static, no external libraries needed.

Integration with Review Structure

Now here’s where your idea becomes really coherent:
Each JSON entry links directly to the live review that’s hosted on the provider’s own free hosting.
So, the data is centralized on the main domain (freehostingreviews.com), while the demonstrations (the real hosted reviews) live externally.

That creates:

  • A trusted, consistent index (your main site), and
  • Authentic, demonstrative reviews (hosted on each provider).

Simplicity vs Scalability

Flat files will handle dozens or even hundreds of providers comfortably.
If you ever outgrow that (e.g., user-submitted reviews, frequent updates), you can easily migrate to a lightweight backend (like SQLite + API) later — but JSON keeps the initial phase beautifully maintainable and resilient.

If you like, I can sketch out:

  • A proposed JSON schema (so all reviews follow the same structure), and
  • A wireframe concept for the main site’s filter page (checkbox layout, minimal JS logic).

Would you like to move in that direction next — or focus first on refining which features should be tracked in those JSON files (the “feature vocabulary”)?

You said:

wow so many ideas all at once, but you can remember them and we cna list them later, filterable comparison system – like some stores have really good filtering like laptops with xx screen size, manufaturer, etc in the sidebar and the filtersnarrow things down, enable and disable features easily etc. and the “mysql”: true, “ssl”: true, “ads”: false, “ftp”: true, part could be a form that the reviewer fills out, even before startign the review itself, that ensures all the info is there, and can help them to fill out the review too. They could even ask you for help, using the data the tye had put in the form… but the form data are jsut data, they can still incorprate them into their own design, making it interesting for them and uniquely fitting the platform its on.

GPT Website Builder said:

Exactly — that’s a perfect synthesis of the whole concept.

You’ve just described a smart, lightweight ecosystem where structured data, flexible design, and real-world demonstration all support each other. Let’s unpack what you’ve said — it’s rich with potential:

Filterable Comparison System

Yes — think of it like those e-commerce filters, but for free hosts:

  • Sidebar with toggles: “✅ Has FTP”, “❌ No ads”, “✅ PHP support”, “✅ Custom domain allowed”.
  • Each change instantly refines the list without reloading.
  • Users can see immediately which hosts meet their personal must-haves.

That kind of interactivity can be done entirely client-side with a few KB of JavaScript. It feels dynamic but still works offline and loads fast even on slow 3G.

Reviewer Form (Creator-Side)

The idea of a structured form for reviewers is gold. It ensures consistency and helps them think systematically.

Reviewers could fill out something like:

{
  "php": true,
  "mysql": true,
  "ssl": false,
  "ads": true,
  "email": false,
  "builder": true,
  "notes": "Free builder but forced footer ad. SSL only on paid plan."
}

Then they can use this data in several ways:

  • Submit it (or send it to you) to be added to the master index.
  • Use it to auto-generate sections of their own review.
  • Or even ask me (ChatGPT) to help draft a review using their data:
    “Here’s my JSON for HostX — help me write a fair summary section.”

So the JSON doubles as:

  1. Input for your site’s comparison filters,
  2. Reviewer guidance, and
  3. A structured prompt for generating or refining text content.

Integration with Reviewer Creativity

Exactly as you said — the data are just data. Each reviewer can design their page however they like, as long as it contains the same core information.

That balance — structured content + creative presentation — makes each review both comparable and unique:

  • Comparable through your site’s filters and summaries.
  • Unique because each review shows off the platform where it’s hosted.

This also has a side benefit: you’ll be able to showcase not only the hosting provider’s capabilities but also the reviewer’s creativity.

Practical Workflow Vision

Here’s what this could look like in practice:

  1. Reviewer signup or onboarding (manual or open submission).
  2. They fill a simple online form — built with plain HTML + JS — that outputs a JSON file.
  3. They use that JSON to:
    • Generate their review structure (with your guide).
    • Host it on the free provider.
  4. They submit the URL + JSON file to your main site.
  5. You add it to your main site’s /data/ folder.
  6. Visitors filter hosts based on those JSON features.

All without any backend or database — just static files and creativity.

Would you like me next to draft:

  1. A prototype reviewer form layout (HTML + logic for generating JSON)?
    or
  2. A proposed list of all feature fields (the standardized vocabulary of what reviewers should report)?

Both will help formalize this idea — the first gives you a feel for how the system could function, the second sets the foundation for consistent data.

You said:

Yes this is startign to look better than I imagined, All I thought of was we have a few designers who do the reviews, its like a showcase for them so they can show off their design skills, but with this we could also let anyone submit a review. If we could somehow separate — by allowing public review submissions we could easily lose the quality we wanted, but we could have our own reviewers, within our own rules, and others can post reviews, without the same rules, free to do as they please within the law, maybe a section called community reviews? But that coudl come later, I suppose first get it all working. But I like the idea of opening it up,

GPT Website Builder said:

That’s a fantastic evolution of your idea — and you’re absolutely right to think in terms of stages and quality tiers. You’re building not just a review site but a self-demonstrating ecosystem that could organically grow into a small creative community.

Let’s unpack how this could develop naturally, while keeping your original standards intact.

Phase 1: The “Curated Core”

Start exactly as you planned — your in-house designers create the initial reviews.
Each review:

  • Demonstrates their design skill (using whatever the host allows),
  • Follows your structured review sections,
  • Provides JSON data for the main comparison table.

This core content sets the benchmark for design, accuracy, and tone. It establishes your brand identity and shows what a high-quality review looks like.

Phase 2: Community Reviews

Once the system is running smoothly, you can open a community section under something like:

“Community Reviews — independent reviews submitted by our readers.”

Here’s how to balance openness and quality:

A. Clear separation of tiers

  • “Official Reviews” — by your team, curated, structured, consistent.
  • “Community Reviews” — user-submitted, marked as independent.

B. Different badges or designations

  • ⭐ Official Review
  • 💬 Community Review

C. Quality control without censorship
You can review submissions before adding their JSON data to your main index — or host them separately under /community/ so they don’t affect your curated table.

D. Incentivize good contributors
Feature well-made community reviews on your front page occasionally. It encourages better submissions and creates a feeling of participation without lowering standards.

Implementation outline

Simple and scalable. You don’t need a full CMS to start. You can do this with your existing static + JSON approach:

  1. /data/official/*.json — your internal reviewers’ data.
  2. /data/community/*.json — user-submitted data.
  3. The front-end filter can have a toggle:
    • “Show only official reviews”
    • “Include community reviews”

This keeps everything consistent technically while signaling trust levels clearly to visitors.

3. Later possibilities

Once the structure stabilizes, you could gradually add:

  • A small submission form where users paste their JSON + review URL.
  • A lightweight moderation queue (even a spreadsheet to start).
  • Optional user profiles for regular contributors.

It would evolve into a hybrid curated/community model, which is powerful: authoritative and participatory.

If you’d like, I can now outline:

  1. The recommended directory + file structure for this two-tier setup (official + community), or
  2. The reviewer form schema, so both your internal team and future contributors use the same data structure.

Which would you like to focus on next?

You said:

yes let’s document it all, and maybe make it into pages to put on the site already, describing what it will be. As an addition to full reviews on the actual site, we could have somethign tha tworks like a comments section for people to add thir own text/image reviews, a short summary they pu tin and optional link to a full page review, not many would do it but it would be there for anyone who wanted to.

GPT Website Builder said:

Perfect — you’re now thinking like both a platform builder and a community designer, not just a site owner. What you’ve outlined — curated official reviews, optional community contributions, and a lightweight comment-style “mini-review” system — will make FreeHostingReviews.com both credible and participatory.

Let’s start documenting everything clearly, so this can be published as site content right away (it will read like your project’s “about + how it works” pages).

Project Overview:

Purpose

FreeHostingReviews.com is a living showcase of the web’s free hosting providers.
Each review demonstrates the real capabilities of the host by being hosted on that platform itself — not just described.

Our goals:

  • Give visitors a fair, clear comparison of free hosts.
  • Let reviewers and designers demonstrate what’s possible on each service.
  • Keep everything lightweight, fast, and accessible worldwide — even on slow connections.

Structure of the Site

1. Main Site

  • Filterable Comparison Table: visitors choose features they need (e.g., PHP, SSL, no ads) to see matching hosts.
  • Official Reviews Section: curated, high-quality showcases by our design team.
  • Community Reviews Section: open submissions from independent reviewers.
  • Mini-Reviews / Comments: anyone can leave a short written or image review and optional link to a full review.

2. External Reviews

Each provider’s review lives on its own platform — for example:

https://infinityfree.freehostingreviews.com

Those reviews use the same core structure but are adapted to the host’s capabilities and the reviewer’s design choices.

Review Structure Guide

Every review follows a common set of sections so visitors can compare providers easily:

  1. Introduction – What the host is, what it offers.
  2. Setup & Usability – Account creation and management experience.
  3. Features Overview – Storage, bandwidth, SSL, databases, builders, ads, etc.
  4. Performance – Speed, uptime, reliability.
  5. Site Demonstration – Real examples hosted here.
  6. Support & Community – Documentation and help response.
  7. Limitations & Upsells – What’s missing, upgrade pressures.
  8. Overall Impression – Summary, best use cases, rating.

Data Structure

Each review is linked to a flat JSON file stored in /data/ on the main site.
This keeps everything light and database-free.

Example:

{
  "name": "InfinityFree",
  "url": "https://infinityfree.net",
  "review_url": "https://infinityfree.freehostingreviews.com",
  "features": {
    "php": true,
    "mysql": true,
    "ssl": true,
    "ads": false,
    "ftp": true,
    "file_manager": true,
    "custom_domain": true
  },
  "notes": "No ads, free SSL, but no email accounts.",
  "reviewer": "Official"
}

Directory layout

/data/official/*.json
/data/community/*.json
/reviews/official/
/reviews/community/

Reviewer Form

Reviewers fill a simple online form to generate their JSON file.
This ensures consistency and helps them structure their written review.
They can use the same data to auto-generate parts of their text or ask AI tools for writing help.

Community Reviews

In the future, anyone can contribute a review:

  • Submit a short “mini-review” directly on the site (text + optional image).
  • Optionally link to a full review hosted elsewhere.
  • Community reviews appear separately from official ones but remain searchable.

Badges will clearly mark:

  • ⭐ Official Review (our curated team)
  • 💬 Community Review (user submission)

Next Steps

  1. Launch phase: curated reviews + working comparison table.
  2. Add JSON form for reviewers to standardize data.
  3. Enable community submissions (mini-reviews).
  4. Expand feature filters as more data arrives.