Inside Spacefast: files, runtime and sharing are separate decisions
A recent Automattic launch shows why a published folder, application runtime and audience need different checks.
Product Hunt’s 12 November 2026 board ranked Spacefast fifth and showed 170 points when checked 13 November. This is a launch signal, not verified adoption or reliability.
Documented components, not a complete production inventory.
- Zero / QuickJS
- Confirmed declared TypeScript runtime compiled into a capsule
- MySQL
- Confirmed per-Space database for the documented Zero route
- Runtime object storage
- Confirmed separation from published version files
A launch with a useful creative job
Product Hunt lists Spacefast by Automattic on its 12 November board. The official homepage offers browser folder or ZIP publishing through drop.fast alongside agent and command-line routes. That gives a designer a route for sharing a small web proof without first running a source build. FreeStack has not published a project to Spacefast or tested its account flow.
Confirmed runtime choices
The official Zero guide describes TypeScript compiled into a capsule, executed in QuickJS beside each Space’s MySQL database. It names tables, live queries, mutations, HTTP endpoints and crons. A version declares Zero or Functions, not both. These are documented platform components, not a claim that every static page uses a database or that the entire production infrastructure has been disclosed.
Uploads are a different storage layer
The storage documentation distinguishes files uploaded by a running application from files included in a published version. Returned object URLs contain a read key. An editorial lesson is to review file access separately from page visibility; a private-looking page alone is not evidence that every referenced file is protected.
The link needs an audience and an owner
The homepage says Spaces start private and can use invitations, share links or public access. It also says unclaimed publications normally expire after 33 hours and 20 minutes from creation or the latest changed-file publish, capped at 30 days. Claiming removes anonymous expiry. These are provider statements, not controls FreeStack has independently penetration-tested.
Free is a bounded hosting allowance
Personal is $0 with $1 usage renewed monthly, one publishing member and 20 Spaces. Usage does not roll over. Published file sizes, traffic and storage have limits; several beta or complimentary resources are only temporarily free. Domain purchase, AI services and higher usage remain separate. This is an ongoing allowance, not unlimited free infrastructure.
Try a smaller workflow first
The linked guide is a FreeStack editorial learning exercise, not Spacefast’s production stack. Use existing catalogue products VS Code and LibreOffice to package a static proof, check relative paths and record a release receipt locally. Then choose a sharing service for the actual audience and requirements. Pay only when those requirements justify it.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.