Old.lat is out: a site publishing platform on your own server
Old.lat is a publishing platform from Oldlee: upload a website ZIP and get a project link on your own domain, with versions, access codes and analytics. No hosted accounts; we offer full source delivery or help with private deployment, priced per project.
Old.lat is out, and the current version is 1.3.0. It is a site publishing platform: zip up a finished website, upload it, and get a project link. Brand pages, client proposals, interactive demos and small trusted PHP projects can all be published, versioned, locked with an access code and tracked from one admin panel.
Unlike a typical hosting service, Old.lat has no public sign-up and no accounts for sale. What we deliver is the program itself: take the source and deploy it yourself, or let us help install it on your server. The program, project files and database stay in an environment you control.
| Item | Details |
|---|---|
| Current version | 1.3.0, October 21, 2026 |
| Runs on | PHP 8.2 + SQLite; verified on Apache / LiteSpeed |
| Admin | Browser-based, Chinese interface, light and dark mode |
| Delivery | Full source delivery, or help with private deployment |
| Price | Quoted per project |
Why we built it
Design and software work often means sending someone a web page: a proposal, a 3D storefront preview, a draft campaign page. Finding hosting and setting up a domain every time is a chore, and on third-party platforms the links and visitor data aren't yours.
Old.lat started as our own publishing tool and was later cleaned up into something other teams can run. It suits design studios that send pages to clients often, brand and marketing teams, and development teams that want this kind of publishing on their own servers.
Upload a ZIP, get a project link
Pack your built site files and upload them. The platform looks for index.html, index.htm or index.php, and recognizes common output folders such as dist, build and out.
- Chunked uploads. Files are split to fit host limits, up to 8 MB per chunk. Defaults are 2 GB per ZIP and 4 GB unpacked; both are configurable, and real limits depend on your host and PHP settings.
- Short links. Leave it blank for an automatic one, or name it yourself.
- What you can publish. Static HTML/CSS/JavaScript, static React or Vue builds (with single-page app fallback), and trusted PHP projects.
- Subpaths. Projects run under a path, so Vite-style projects should use relative asset paths, such as base: "./".
Update without changing the link, and keep the data
Every release creates a new version while the project link stays the same. Updating is the main change in 1.3.0:
- Overwrite update (default). Keeps the runtime data it detects. When names clash, data files keep the current version's content and code files come from the new package.
- Clean replace. Uses only the new package, with no old data.
- Deployment file manifest. From 1.3.0 every deployment records a file list used to tell runtime data apart; older versions have no manifest, so modification times are used as an estimate.
- Versions page. View data, preview a restore, and delete versions that aren't current. Files overwritten by a restore go to a recycle bin for 30 days. The number of kept versions is capped.
The migration logic passed all 26 data migration checks in an isolated environment, and data viewing and restore preview work on the live server. We have not yet restored real business data with it, so please back up important projects before updating.
Access codes, analytics and admin security
- Access codes. When on, the full share link carries a random code. A missing or wrong code, an offline project and a project that doesn't exist all show the same 404. You can rotate the code, set an expiry, take a project offline, and copy the link or a QR code.
- Analytics. Views, visitors, referrers, devices, browsers, time on page, scroll depth, visit paths and click heatmaps, stored on your own server. Location lookup can use a local MMDB database instead of an external API. Retention and IP masking are configurable; analytics may still record IPs, so configure it for your actual use and tell visitors.
- Admin sign-in. Password plus Authenticator code, with recovery codes and sign-in history.
- Backups. Download a SQLite database backup. A full restore also needs the program configuration and project files. Keep the data folder outside the web root when you deploy.
- Languages. The public homepage and 404 page come in Simplified Chinese, Traditional Chinese, English and Japanese; the admin panel is Chinese only for now.
What it can't do yet
- One admin account only: no team roles, approval flow or enterprise SSO.
- An access code is not identity verification: anyone with the full link can forward it.
- No long-running Node services, server-side rendering or containers; export those projects to static sites first.
- Path-based links only, no automatic per-project subdomains.
- Built for individuals, studios and small teams, with no promise of large-scale high traffic. PHP execution is not a sandbox; only deploy trusted code.
- No public sign-up and no free self-serve hosting.
How to get it
There are two options: full source delivery, for teams with development and operations skills who want to deploy and maintain it themselves; and private deployment, where we assess your environment, install it on your server, and hand over after agreed acceptance checks.
Both are quoted per project. License scope, number of installations, migration, branding, maintenance and support period are listed item by item in the quote, as is whether domains, hosting and third-party costs are included. Before deployment you'll need your own domain, a compatible PHP host, a TLS certificate and a writable data folder.
To learn more, see the Old.lat product page or the public homepage at old.lat, then reach us on Telegram.
