New: Oldview, a free image viewer for Windows. Version 0.4.1 is out. Take a look

Old.lat

Site publishing · source + deployment Business

Your site platform.
On your own server.

Turn website ZIPs into links on your own domain. Publish landing pages, client proposals, interactive demos and trusted PHP projects with versions, access codes and first-party analytics.

Oldlee offers complete source delivery or help with private deployment for businesses, studios and development teams. You control the program, project files and database. Scope and pricing are agreed per project.

  • Browser administration
  • PHP 8.2 + SQLite
  • Your domain and server
old.lat
Old.lat concept diagram: a ZIP becomes a project link through your own server
2 GB
Default ZIP limit; hosting resources apply
4
Public homepage and 404 languages
2 steps
Password + Authenticator sign-in
01

Complete source for your team

Receive the publishing platform source, deployment package and setup notes. Run it on your own domain and server, or ask Oldlee to help deploy it. Built for businesses and studios that publish proposals, campaign pages and web demos repeatedly. License scope, installation count, branding and support are agreed in the quotation.

Architecture diagram: program, project files and SQLite data stay in the customer environment
02

Upload a ZIP. Get a project link.

Upload built website files. Old.lat finds index.html, index.htm or index.php, including common dist, build and out folders. Uploads use chunks of up to 8 MB, adjusted to host limits. Leave the slug blank to generate one or choose your own. Supports static sites, SPA fallbacks and trusted PHP projects.

Actual deployment screen with ZIP upload, slug, access code, SPA fallback and PHP options
03

Keep versions. Keep the link.

Each release creates a version; choose how many to retain. Switching versions keeps the project link. PHP projects attempt to carry runtime-written files forward, while matching files supplied in the new ZIP take priority. Back up and test projects that contain important settings or uploads before changing versions.

Version workflow illustration: retain v1 and v2, publish v3, keep the project path
04

Share private work with an access code

Public projects open directly. With an access code enabled, the full share link contains a random code. Missing or wrong codes, offline projects and unknown paths return the same 404. Rotate codes, set expiry, take a project offline or copy a link and QR code. Anyone holding the full link can forward it; this is not enterprise identity verification.

Access flow: missing or wrong codes return 404; a valid share link opens the project
05

Analytics on your own server

Built-in views, visitors, sources, devices, browsers, foreground time, scroll depth, visit paths and click maps. Optional local MMDB data provides GeoIP without an external lookup API. Configure retention and IP masking. Analytics may still record IP and other visit details, so configure and disclose collection for your use case.

Analytics capability diagram with visit paths, sources, click maps and offline GeoIP; no customer data
06

Two-factor admin access and backups

Administrator sign-in uses a password and an Authenticator code, with recovery codes and sign-in records. The server stores the database, project versions, sessions and runtime files; deployment should place private data outside the web root. Download a SQLite backup; a complete recovery also needs configuration and project files.

Security diagram: password and TOTP sign-in with private database, versions and backup storage
07

Four public languages. A focused console.

The homepage and 404 page support Simplified Chinese, Traditional Chinese, English and Japanese, with remembered language selection. The admin console is in Chinese and supports light and dark modes. PHP and SQLite power the platform without a persistent Node service. Deployment starts with your domain and compatible hosting.

Actual Old.lat homepage showing language choice, theme control and product introduction

Specs & requirements

Current version
1.2.0
Server
Deployed and checked on PHP 8.2 with Apache / LiteSpeed .htaccess routing. Other servers need routing adaptation.
Required components
PDO SQLite, ZipArchive and mbstring; writable project, temporary-file and session directories.
Storage
SQLite WAL and local project files. Keep private data outside the web root where possible.
Project types
Built HTML / CSS / JavaScript; trusted PHP projects; SPA route fallback.
Default upload limits
2 GB ZIP, 4 GB extracted, chunks up to 8 MB. Configurable; actual limits depend on hosting resources and PHP.
Domains and languages
Path-based links on your domain. Homepage and 404: Simplified Chinese, Traditional Chinese, English and Japanese. Console: Chinese.
Delivery
Complete program source or assisted private deployment. Domain, hosting, license, customization and maintenance scope are quoted separately.

What it can’t do yet

Better you know now than after you install it.

  • One administrator account today. No team roles, approval workflows or enterprise SSO. Access codes are not an identity-based permission system.
  • No persistent Node services, server-side rendering or container workloads. Export compatible static files before uploading these frameworks.
  • Current links use paths, without automatic project subdomains. Domain, DNS and TLS behavior depend on the hosting environment.
  • Intended for individuals, studios and small teams; no large-scale concurrency promise. PHP execution is not a sandbox for untrusted code.
  • Project ZIP exports in v1.2.0 were reported canceled by the browser in the current environment and are not accepted as verified delivery. Database backup has been checked.
  • No public registration or free self-service hosting. Domain, server, backup operations, customization and support term must be specified in the project scope.

Pricing

Complete source delivery

For teams with development and operations skills that want to deploy and maintain the platform themselves.

Project quotation

  • Complete platform source and deployment ZIP
  • Setup notes and version handover records
  • Your domain and compatible hosting
  • License, modifications and support agreed separately
Ask about source delivery

Private deployment

For businesses and studios that want Oldlee to help assess the environment, deploy and hand over the platform.

Project quotation

  • Environment and requirements assessment
  • Installation in your own environment
  • Agreed acceptance checks and handover
  • Migration, branding and maintenance by agreement
Discuss private deployment

Both options are quoted per project, based on licensing and installation count, your environment, branding, migration and support. This page does not promise free hosting, unlimited maintenance or lifetime updates. The quotation states whether domain, hosting and third-party costs are included.

Old.lat

Request a demo

Tell us about your team. We’ll book a live walkthrough and answer questions about deployment and pricing.

Or email us directly:
lee@eeoo.dev

Team size
Deployment

FAQ

Am I buying source code or a hosting account?

The main options are complete source delivery and private deployment. Run a publishing platform on your own domain and server; this is not a public self-service hosting account on old.lat. Deliverables, licensing and support are agreed per project.

What can I publish?

ZIP the built HTML, CSS, JavaScript and assets. Static React or Vue builds can use SPA fallback. Trusted PHP entry projects are supported. Applications requiring a persistent Node service are not. For subpath hosting, configure relative asset paths, such as Vite base: "./".

What does private deployment require?

Your domain, compatible PHP hosting, a TLS certificate and writable data storage. The checked environment uses PHP 8.2, PDO SQLite, ZipArchive and mbstring. Permissions, routing and capacity are assessed before agreeing scope. Other environments need compatibility work.

Can someone forward a private link?

Yes. The code is part of the full share link, so anyone holding it can forward it. Rotate the code, set expiry or take the project offline. It does not provide enterprise user identity checks or replace SSO and confidentiality practices.

How are data kept across releases or migration?

Version handling attempts to carry PHP runtime files forward, but matching files in the new ZIP take priority. Back up and test important projects. Complete migration needs platform configuration, database and project files together; SQLite alone is not a complete business backup.

What is included in the price?

Source delivery and private deployment are quoted per project. We confirm licensing, installation count, migration, branding and the maintenance and support term before quoting. This page does not replace an agreed statement of work.

Changelog

  1. 1.2.0

    Path-based publishing, public languages and database backup

    • Standardized path-based project links and removed subdomain and cPanel API settings.
    • Rebuilt the public homepage with four homepage and 404 languages; fixed navigation clicks and anchor positioning after scrolling.
    • Added SQLite backup download, checked for successful download and database integrity in the current environment.
    • Added version ZIP export controls; browser downloads were reported canceled in the current environment, so this remains unverified.

Old.lat

Your site platform.
On your own server.

More from Oldlee