Free hosting: everything it includes

What you get

A separate process per customer is not a formality. It means somebody else’s site caught in an endless loop takes neither memory nor time from yours: each has its own ceiling and each hits it alone.

Disk space

500 MB

MySQL database

one, up to 200 MB

PHP

8.4, a separate process for each customer

Memory per request

128 MB

Script run time

up to 60 seconds

File upload

up to 64 MB

Traffic

neither counted nor capped

Your own domains

as many as you like, all showing one site

HTTPS certificate

issued and renewed by itself

Term

indefinite, as long as you sign in to the mailbox

Getting started

1. Account → Hosting → Get space. It takes seconds; there is nothing to approve.
2. The credentials appear in the same place: login, file manager address, database details.
3. Open the file manager and upload your site into the public_html folder.
4. The site is immediately live at an address like s-login.andevora.com — something to show while your own domain is not yet attached.

A file manager instead of FTP

Files go up through a manager in the browser: by dragging, by folders, by archive. An archive can be unpacked on the server without unpacking it on your own machine first.

There is no FTP or SFTP, deliberately. FTP sends the password in the clear, and SFTP would mean a system account for every customer — which is exactly the door through which free platforms turn into nurseries for abuse. The manager does the same job and opens nothing extra.

Database and phpMyAdmin

The database is created together with the space. Its name, user and password sit in the same credentials as everything else.

You manage it through phpMyAdmin in the browser — import, export, editing tables, all the familiar things. Nothing to install; it already runs at db.andevora.com.

From your code, connect to localhost: the database sits on the same server as the site and is not exposed outside.

What PHP can do here

Version 8.4 — current, not the one older platforms are still clinging to. The usual extensions are all present:

1. Databases: mysqli, PDO, pdo_mysql.
2. Images: gd, exif.
3. Network and data: curl, openssl, sodium, json, xml, dom, simplexml, xsl.
4. Text and languages: mbstring, iconv, intl, gettext.
5. And: zip, bcmath, fileinfo, OPcache.

Your own domain

Attaching takes two steps: first add the domain in your account, then point it at our nameservers with your registrar. The details are in a guide of its own, "Attach your own domain".

We create the zone, sign it with DNSSEC and issue the certificate. All you provide is two lines in the registrar’s panel.

HTTPS without you lifting a finger

The certificate is issued automatically as soon as the domain starts pointing at us, and renews itself every three months. No expiry to watch, nothing to pay.

Plain http is forced over to https: your visitors get no unencrypted version.

What is not here, and why

Half of that list is not meanness but the condition on which a platform can stay free and still not spew spam. Mail from code is the main way free hosting earns a bad name, and we closed it entirely rather than limiting it.

1. FTP and SFTP — see above; a file manager instead.
2. .htaccess — the platform runs nginx, not Apache, and that file is simply never read. Redirect rules belong in your application.
3. SSH — customers have no shell on the system.
4. Your own scheduled jobs — we do not hand out cron.
5. Sending mail from scripts — the mail function is switched off and there is no mail program on the server. You can write only from your own mailbox, signed in.
6. IPv6 — not switched on yet.

What it suits

A personal page, a calling card, a portfolio, a small blog, a study project, a landing page, a small organisation’s site — all of these live comfortably in 500 megabytes.

What it does not suit: a shop with thousands of items, video hosting, a file dump, anything under constant heavy load. Not because it is forbidden, but because it will hit the ceilings and run badly — for you and for the neighbours.