Spacefast: Automattic’s New Static Hosting  🔗 **Source:** [Spacefast: Automattic’s New Static Hosting](https://www.youtube.com/watch?v=REtN7aXwBLA) > [!note]+ Document Notes > tags: [static-hosting, automattic, spacefast, wordpress-static-sites, agentic-deployment, cloudflare-alternatives] > author: WP Minute Tutorials > source: WP Minute Tutorials (YouTube) > reference: https://www.youtube.com/watch?v=REtN7aXwBLA > date created: 2026-09-29 10:32 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > # 🏷️ Title: Spacefast: Automattic’s New Static Hosting (Cloudflare/Vercel Alternative?) > <!-- deep-read:sections start --> ## 🧭 Table of contents - [📝 Summary](#-summary) - [📖 Main content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning styles assessment](#-learning-styles-assessment) - [📊 Accessibility assessment](#-accessibility-assessment) - [🌍 DEIB assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🛡️ DARVO analysis](#️-darvo-analysis) - [🎯 Conclusion](#-conclusion) - [🔄 Refactor appendix](#-refactor-appendix--spacefast-automattics-new-static-hosting-cloudflarevercel-alternative) ## 📝 Summary - **What happened.** WP Minute Tutorials published a 15:00 first-look video on 2026-09-28 (697 views at capture) of Spacefast (spacefast.com), a hosting product from Automattic. The narrator builds three test projects: a static landing page, a full-stack to-do app, and a static export of a local WordPress site. The narrator calls it a "preview video," not a deep dive. - **Caption note.** The auto-captions render Automattic as "Automatic" throughout, the product mostly as "Spacefast" but once as "Space Fast," and garble several other terms: "Gentic" and "Agility Builder" (likely "Agentic" and "Agentic Builder," referring to Automattic's AI site builder in the Studio app), "S2" (an attempt at S3), and "Superbase" (Supabase). This analysis uses the metadata and description form "Spacefast" and preserves caption spelling only inside quote blocks. - **The claim.** Spacefast is a simpler alternative to Cloudflare and Vercel for developers who don't want a large infrastructure console. The narrator reports a Free tier, a $5 per month "Go" tier, and a team tier from $15 per month, and says the $5 entry price matches Cloudflare's paid Workers plan. These numbers come from the narrator's read of the pricing page and aren't checked here. - **What it does, as shown.** Deploys from a zip drop, a Git push, or the Spacefast command line. Hosts static sites (Astro is named in the docs), full-stack apps with storage and a MySQL database, and static front ends for WordPress through a plugin. Agent connections are a first-class feature, and the dashboard tracks which agents are connected. - **Why it matters.** It's Automattic entering the static and agent-built site market that WordPress hosts are losing sites to. The narrator's thesis: people who leave WordPress for bespoke JavaScript sites also leave behind the application layer (users, permissions, content tooling), and Spacefast tries to rebuild some of it. - **Key stakeholders.** Automattic (vendor), the narrator and The WP Minute team (publisher, unnamed on the transcript apart from editor Eric Karkovack), agencies moving clients to static or agent-built sites, WordPress hosts, and the maker of the Simply Static plugin that the Spacefast plugin installs. - **Risks and tradeoffs.** Three features (storage, database, users) are labeled beta. The narrator couldn't get the WordPress export to work a second time, couldn't get email magic-link auth for their app, and says the testing ran against localhost, not a public HTTPS domain. Every result is one person's first run on an early product. - **Bottom line.** Worth watching, too early to rely on for client sites. The static and full-stack paths worked in the demo. The WordPress static path is the one to re-test on a real domain before drawing conclusions. ## 📖 Main content **The pitch.** The narrator first assumed Spacefast was a static site builder, then decides it's a hosting and platform play aimed at the same buyers as Cloudflare and Vercel. The narrator's framing of Cloudflare: mature, second only to Amazon or Google Cloud in breadth, and hard to work with unless you know infrastructure. Spacefast, in the narrator's view, simplifies that experience and should stay in that lane. The narrator notes it may just be early, and that the dashboard doesn't overwhelm the way Cloudflare's does. **Pricing and publishing.** Free to start, $5 per month for Go, $15 per month and up for teams. You deploy by dropping a zip of HTML or an app, by connecting Git, or by pushing from the command line. Treat the prices as reported, not verified. **Agents first.** The narrator says the docs and dashboard push you to copy instructions and hand them to an agent. The dashboard shows which agents are connected and what they're doing. Connectors are "limited to the big players" (the narrator names Google and Cloudflare), with webhooks, account variables, and secrets alongside. Each project is called a "space." **Three projects tested.** - **Static site.** Built with Codex plus the Spacefast command line from a prompt asking for a landing page for a WordPress web agency. It deployed without trouble. The project view shows files, builds, domain registration, traffic routes, environment variables, 404 pages, favicons, Google Analytics, and custom header JavaScript. The narrator pressed the agent for a blog model. It first suggested WordPress, then agreed to ingest Markdown files and deploy through a GitHub Action. The narrator also says the docs cover hosting an Astro site. - **Full-stack to-do app.** Built from a one-line prompt, storing tasks in a MySQL database that Spacefast provides. Storage (which the narrator compares to Amazon S3 and Cloudflare R2), the database, and user management sit under a beta label. The narrator pins their confusion on auth: login options had dropped to a wordpress.com login (an earlier build had a Gravatar toggle), and the agent said Spacefast auth was for people logging in to Spacefast, not for an app's own users. A Google app connection could presumably supply Google sign-in. - **Static WordPress.** Built locally in the WordPress Studio app, using Automattic's AI site building tied to wordpress.com credits. The Spacefast plugin installs Simply Static. One deploy pushed about 1,700 files and took a long time. It worked once and the narrator couldn't repeat it, in roughly seven tries. The narrator notes localhost isn't a real HTTPS domain and wonders whether Simply Static Pro is needed. **The WordPress angle.** The narrator's scenario: run WordPress privately (on a desktop or behind a firewall), publish only the static output to Spacefast, and cut both cost and public exposure. The narrator says this is what many people will want once it's reliable. **The auth angle.** The narrator treats user management as the underrated part of WordPress. People leaving for static sites end up buying a CRM billed by seat or building auth on something like Supabase (the caption says "Superbase"), which adds another infrastructure layer to manage. Spacefast appears to understand this, with wordpress.com and Gravatar as a possible identity layer. **Contested or unverifiable in this source.** Prices, the Simply Static ownership detail (narrator: co-founder of the Ollie theme, "I believe"), the beta status of each feature, and the claim that the WordPress export is unreliable versus misconfigured are all unconfirmed. The narrator describes several results as possible "user error." The narrator also says Automattic didn't ask the narrator to cover this and that they asked for access on their own. ## 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=REtN7aXwBLA&t=0) What is Spacefast - Announces a preview of spacefast.com from Automattic, the company behind wordpress.com, Tumblr, and Pocket Casts. The caption spells the company "Automatic." - Says agentic static-site building is a growing movement, and WordPress is in its crosshairs. > [!quote] [00:00:00] > It's their latest offering into which at first I thought was just a static site builder. #### ⏱️ [00:00:40](https://www.youtube.com/watch?v=REtN7aXwBLA&t=40) Why it matters - Positions Spacefast against Cloudflare and Vercel, the static hosting incumbents of roughly a decade. - Argues Cloudflare's breadth (compared with Amazon and Google Cloud) burdens people who aren't seasoned in infrastructure. - Reads Spacefast as a deliberate simplification and says it should stay the easier-to-use option. > [!quote] [00:00:42] > It looks like a way to compete against the Cloudflares, the Vercels, the static hosting solutions that have dominated the market #### ⏱️ [00:01:49](https://www.youtube.com/watch?v=REtN7aXwBLA&t=109) Pricing and publishing - Tiers as reported: free, Go at $5 per month, teams from $15 per month. The narrator compares the $5 entry to Cloudflare's Workers paid plan. - Publish paths: zip of HTML or an app, Git connection, or command line push. - The narrator's view: people leaving WordPress for Cloudflare or Vercel lose the easy application layer and end up depending on infrastructure support. > [!quote] [00:02:09] > drop files in like a zip file of HTML or an app, whatever, drop it in, it'll deploy it and host it #### ⏱️ [00:03:05](https://www.youtube.com/watch?v=REtN7aXwBLA&t=185) Dashboard and agents - Projects are called spaces. The dashboard shows connected agents and their activity. - Docs and UI repeatedly tell you to copy instructions to your agent. - Connectors are limited to big vendors, with webhooks, account variables, and secrets. Git push and file drop both create spaces. - Bug the narrator hit: the drop or push screen created an extra space (three became four). The narrator deleted it on camera to show the delete flow. - Hand-drawn icons look quirky. A lock icon means the space isn't published. > [!quote] [00:02:52] > they're definitely leaning into the agent side of this first and foremost. #### ⏱️ [00:05:01](https://www.youtube.com/watch?v=REtN7aXwBLA&t=301) Project types overview - Three projects: a static site, a full-stack app, a static WordPress site. - The narrator's scenario: host WordPress privately, publish static output, cut cost and reduce public exposure. > [!quote] [00:05:01] > Host a WordPress site internally or somewhere on your desktop or on a sort of behind a firewall #### ⏱️ [00:05:51](https://www.youtube.com/watch?v=REtN7aXwBLA&t=351) Static site demo - The preview screen shows a WordPress logo, which the narrator takes as a sign the product borrows Automattic's managed WordPress infrastructure. That's an inference, not a stated fact. - Built with Codex plus the Spacefast command line from a prompt for a WordPress agency landing page. - Asked about blogging, the agent first recommended WordPress, then agreed to Markdown ingestion via a GitHub Action. - Project settings shown: files, builds, domains, traffic routes, environment variables, 404 pages, favicons, Google Analytics, custom header JavaScript. > [!quote] [00:05:44] > So, I created this project or this static site through the command line and the power of Codex. > [!quote] [00:06:27] > And the first thing it did was might want to consider WordPress. #### ⏱️ [00:08:36](https://www.youtube.com/watch?v=REtN7aXwBLA&t=516) Full-stack to-do app - One-line prompt produced a JavaScript to-do app saving to a database. - Three areas carry a beta label: storage, database, and (by context) users. - Storage is compared to Amazon S3 and Cloudflare R2. The caption says "S2." - The narrator adds a task ("Matt's second item") and sees it in the MySQL view. > [!quote] [00:09:18] > Has a MySQL database, which you can see right here #### ⏱️ [00:09:42](https://www.youtube.com/watch?v=REtN7aXwBLA&t=582) Auth and users questions - A Gravatar login toggle the narrator saw earlier is gone. The option now reads wordpress.com login. - Asked the tool to build email magic-link sign-in for app users. It said that isn't what Spacefast auth is for. - Google sign-in looks possible by registering a Google app. - Argues auth is undersold in WordPress. Alternatives are seat-priced CRMs or self-managed auth on Supabase-type services. > [!quote] [00:10:00] > the Gravatar and wordpress.com thing is interesting when you start to think of wordpress.com and and Gravatar as the authentication layer #### ⏱️ [00:11:29](https://www.youtube.com/watch?v=REtN7aXwBLA&t=689) WordPress static hosting - Built in the Studio app with Automattic's agentic builder (captions: "Gentic" and "Agility Builder"), paid by wordpress.com credits. - The Spacefast plugin also installs Simply Static, which the narrator attributes to a co-founder of the Ollie theme "I believe." The narrator wonders whether Automattic will keep recommending, buy, or fork it. - One deploy pushed about 1,700 files and was slow. It worked once and the narrator couldn't repeat it. - Caveat: localhost, not a public HTTPS domain. The narrator suggests trying a domain behind password protection, or Simply Static Pro. - The narrator drove much of the testing through the Spacefast command line, which the narrator calls "really good." > [!quote] [00:11:25] > Now, this is the one where I had the the most issues and I just don't know if it's ready for prime time yet. > [!quote] [00:12:07] > it worked once and I couldn't get it to work again. > [!quote] [00:12:50] > It's not a hosted HTTPS site with a real domain that's connected to the internet. #### ⏱️ [00:14:03](https://www.youtube.com/watch?v=REtN7aXwBLA&t=843) Wrap up and feedback - Summary: static front end for WordPress "once it's nice and clean," full-stack apps, and static apps including Astro. - Asks Automattic staff to reach out. The narrator says nobody asked them to cover Spacefast and they requested access on their own. > [!quote] [00:13:33] > Pretty interesting play from Automatic. #### ⏱️ [00:14:32](https://www.youtube.com/watch?v=REtN7aXwBLA&t=872) Subscribe and newsletter - Promotes thewpminute.com, its newsletter, and its team of podcast, video, and blog contributors. Names Eric Karkovack as editor and practicing agency owner. - Ends at thewpminute.com/subscribe. ## 📚 References The transcript itself contains no links; the following come from the video description or are primary sources for named entities. - [Spacefast: Automattic’s New Static Hosting (Cloudflare/Vercel Alternative?)](https://www.youtube.com/watch?v=REtN7aXwBLA) — the source video, 15:00, uploaded 2026-09-28 by WP Minute Tutorials. - [spacefast.com](https://spacefast.com) — the product reviewed; named in the description and in the video. - [The WP Minute](https://thewpminute.com/) — WordPress news, from the description. - [The WP Minute newsletter](https://thewpminute.com/subscribe/) — subscription page, from the description and the spoken close. - [Support The WP Minute](https://thewpminute.com/support/) — donation and membership link, from the description. - [Automattic](https://automattic.com) — vendor. The captions spell it "Automatic." - [WordPress Studio](https://developer.wordpress.com/studio/) — the local WordPress app the narrator used for the static WordPress test. - [Simply Static](https://wordpress.org/plugins/simply-static/) — the static export plugin the Spacefast plugin installs. Maintainer and ownership claims in the video aren't verified here. - [Astro](https://astro.build) — static site framework the narrator says the Spacefast docs cover. - [Cloudflare Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/) — check the $5 per month comparison against the source. - [Gravatar](https://gravatar.com) and [wordpress.com](https://wordpress.com) — the identity options discussed for app login. ## 🗣️ Paraphrase The narrator spends 15 minutes testing Automattic's new hosting product, Spacefast, and the headline is that it's a simpler, agent-friendly alternative to Cloudflare and Vercel, not a WordPress product. You can drop a zip, connect Git, or push from a terminal, and the whole interface nudges you to hand the work to a coding agent. The cost sits at $5 per month for the first paid tier, by the narrator's reading of the pricing page. The narrator then tests it three ways. A static landing page built with Codex deploys cleanly. A to-do app with a MySQL database works, though the beta storage, database, and users features leave them unsure how app-level login is supposed to work, especially after a Gravatar option disappeared and the tool told them Spacefast auth is for Spacefast users. The static WordPress export, which pushed about 1,700 files from a local Studio site, worked once and then wouldn't repeat. The narrator's forecast is conditional. If the WordPress path gets reliable, agencies could keep WordPress behind a firewall and publish only static files, cutting cost and exposure. The narrator also thinks user management is the part of WordPress that static-site converts underrate, and that Spacefast seems to see it. ## 📰 Newsletter **Automattic's new hosting play, tested by someone who wasn't invited.** The WP Minute Tutorials channel got early access to Spacefast, and the 15-minute preview is worth your time if you build for clients. The pitch: static sites, full-stack apps, and static exports of WordPress on one simpler platform, with agents as the primary user. The reported pricing is free, then $5 per month, then $15 per month for teams. What worked: a Codex-built agency landing page deployed on the first try, and a to-do app saved rows to a MySQL database. What didn't: the WordPress static export worked once out of roughly seven tries, and app-level login was confusing. Storage, database, and users all carry beta labels, so treat this as a look ahead, not a migration plan. The idea to steal is the private-WordPress, public-static pattern. Keep the editor behind a firewall, publish HTML, and shrink your attack surface. Links: [the video](https://www.youtube.com/watch?v=REtN7aXwBLA), [The WP Minute](https://thewpminute.com/), [spacefast.com](https://spacefast.com). ## ✅ Action items #### DevRel - Developer advocacy: record a repeatable Spacefast test of the same static, full-stack, and WordPress paths on a public HTTPS domain, and publish exact results per path so the localhost caveat is removed. - Education: run an office-hours session on "private WordPress, public static," using the 1,700-file export as the worked example. - Developer experience: file a docs bug for the auth flow. The video shows the Gravatar toggle vanishing and an agent saying app-user login isn't supported. - Developer marketing: don't cite the $5 and $15 prices from this video. Pull them from the official pricing page with a retrieval date. - Community management: when the video circulates, add a note that the narrator calls several results possible user error. - Internal/external/cross-project: send the narrator's feedback (extra space created by the drop screen, unclear beta labels) to an Automattic contact through the channel the narrator asked for. #### OSPO - Policy and governance: decide whether a vendor-hosted static platform is allowed for project sites, and write the criteria (export, domain ownership, data location). - License compliance: review Simply Static's license and any Spacefast plugin bundling terms before recommending the plugin pair. - Security management: agent-driven deploys mean an agent holds deploy credentials. Document token scope and rotation before adoption. - Software inventory: list Spacefast as a hosting dependency with an owner and an exit plan if it's ever used. - Developer support: write guidance on what "beta" means for storage, database, and users on any platform, including data-loss expectations. - Community engagement: no direct action from this source; nearest relevance is asking Automattic how upstream plugins like Simply Static are supported. - Strategic alignment: add "static export reliability" as a tracked metric if static WordPress publishing becomes a recommended path. #### Community - Maintainers: no direct action from this source; nearest relevance is a documentation site that could publish as static files. - Contributors: no direct action from this source; nearest relevance is a first-issue task to test a static export of a small site. - Sponsors: no direct action from this source; nearest relevance is hosting credits from vendors, which should be disclosed. - Ecosystem: run a shared test of static WordPress export across Simply Static, hosted static platforms, and Playground, so results are comparable. #### WordPress - Core: no direct action from this source; nearest relevance is that static publishing shifts load off PHP and the database. - Core Performance: measure a static export against the same site served dynamically, since the narrator's 1,700-file push is a size datapoint, not a performance one. - Core AI: note the agent recommended WordPress when asked about blogging, then adapted to Markdown. Track how agents route users between WordPress and static stacks. - **Core Program Team:** no direct action from this source; nearest relevance is cross-team awareness that a major host is courting agent-built static sites. - Mobile: no direct action from this source. - Playground: Playground already runs WordPress in the browser. Test whether a Playground site can export static files to a Spacefast-style host. - Community: no direct action from this source; nearest relevance is a meetup talk on "private WordPress, public static." - Training: draft a lesson on choosing between dynamic WordPress, static export, and a full-stack app. The three-project structure of this video is a ready outline. - Marketing: no direct action from this source; nearest relevance is messaging for agencies who keep WordPress as the editor. - Support: prepare a canned answer for "should I move my site to a static host," including the user-management tradeoff the narrator raises. - Design: no direct action from this source. - Documentation: document static export steps and their known failure points, including localhost limits and file counts. - Photos: no direct action from this source. - TV: no direct action from this source. - Polyglots: no direct action from this source. - Accessibility: audit a static export for accessibility parity with the dynamic site, including forms that need a backend. - Meta: no direct action from this source. - CLI: check whether a WP-CLI command could trigger and verify a static export, so the flaky admin path isn't the only route. - Hosting: compare the reported $5 per month tier with hosts' static offerings, using verified prices. - Tide: no direct action from this source. - Openverse: no direct action from this source. - Themes: test block themes under static export for missing assets and relative URL issues. - Plugins: examine how static export plugins handle forms, search, and comments, which the video doesn't cover. #### The WPOCC - Programs: no direct action from this source; nearest relevance is a microgrant for static export reliability testing. - Projects: no direct action from this source. - Funding experiments: if The WP Open Community Collective funds infrastructure, ask vendors like Automattic to disclose credits and terms. ### FAIR - Technical independence: static exports are portable files, which supports host independence. Verify that a Spacefast export leaves no proprietary dependency behind. - Policies and covenants: no direct action from this source; nearest relevance is an operator expectation that hosted platforms document export and exit paths. - Productized governance artifacts: add "static hosting dependency" to operator scorecards. ## 🧪 Hypotheses 1. On a public HTTPS domain, a static WordPress export to Spacefast succeeds on at least 9 of 10 consecutive deploys, so the narrator's 1-of-7 result comes from localhost and configuration, not the product. 2. A static export of a typical agency WordPress site produces between 1,000 and 3,000 files, and deploy time scales with file count. 3. A Codex-generated static landing page reaches a passing Lighthouse performance score of 90 or higher on Spacefast with no manual tuning. 4. App-level email magic-link login isn't achievable with Spacefast's built-in auth alone and needs a third-party provider. 5. Agents recommend WordPress for blog requirements in more than half of trials on this platform, matching the narrator's first-response result. 6. Storage, database, and users leave beta within 6 months, judged by label changes on the product pages. ## 📊 Methodology - **H1.** Register a test domain, install the Spacefast plugin on a clean WordPress site, and run 10 deploys with unchanged content. Log success, duration, and error text. Repeat with Simply Static Pro to separate the plugin variable. - **H2.** Export 20 real sites of varied size and record file count, total bytes, and deploy time. Fit a line and report the correlation. - **H3.** Generate the same landing page prompt in 5 agent runs, deploy each, and run Lighthouse 3 times per deploy from a fixed location. - **H4.** Read the auth docs, then attempt the magic-link flow with a scripted test user. Record what fails and whether an external provider closes the gap. - **H5.** Run the blog prompt 20 times with a fixed agent and model, and classify each first answer as WordPress, Markdown, or other. - **H6.** Snapshot the product docs and pricing pages monthly, compare labels, and record dates. - **Controls.** Fix agent version, prompt text, region, and account tier. State the retrieval date for every price. ## ❓ Questions - Is the extra space created by the drop or push screen a bug or an intended draft state? - Which of storage, database, and users are actually in beta, and what are the data-durability terms? - Is Spacefast built on Automattic's managed WordPress infrastructure, or does the WordPress logo in the preview screen mean something else? - What does the wordpress.com login option cover, and is Gravatar sign-in for an app's own users coming back? - Does the Spacefast plugin bundle, depend on, or fork Simply Static, and who supports failures? - Why did the export fail after the first success: rate limits, file counts, localhost, or plugin state? - What is the pricing basis for the $5 and $15 tiers (requests, storage, seats)? - Can WordPress forms, search, and comments work on a static export, or do they need external services? ## 🔮 Future research - **Static export reliability at scale.** No source here measures success rate across sites, and the narrator's account is one person on localhost. - **Agent-built site security.** Deploy-capable agents hold credentials. Nobody in this video discusses token scope or review gates. - **Identity for static sites.** The narrator's point that user management is underrated deserves a comparison of Gravatar, wordpress.com, Supabase-type services, and seat-priced CRMs on cost and control. - **Platform lock-in.** Compare how easily a Spacefast site moves to Cloudflare or Vercel, and back. - **Private-editor, public-static pattern.** Measure the actual reduction in attack surface and hosting cost, which the video asserts and doesn't quantify. ## 💡 Implications - **Practice.** Agencies can test a private-WordPress, public-static workflow now, but only with a fallback host and a real domain. - **Policy.** Teams adopting agent-driven deploys need a written rule for who can publish, what credentials the agent holds, and how a bad deploy is reverted. - **Security.** Removing a public WordPress admin shrinks the exposed surface. A deploy token in an agent's hands adds a new one. - **Education.** The three-project structure (static, full-stack, WordPress export) works as a lesson outline for choosing an architecture. - **Funding.** If hosts compete on $5 entry prices, plugin maintainers whose tools power static export, such as Simply Static, become important dependencies and need support. - **Vendor literacy.** The narrator states they asked for access and weren't asked to cover the product, and they report failures on camera. That disclosure model is worth copying. ## 🧠 Learning styles assessment - **Reading level estimate.** I computed Flesch-Kincaid Grade Level on the caption text (2,882 words, 200 sentences split on punctuation): about grade 5.9, Flesch Reading Ease about 79. Run-on speech and no periods in places inflate sentence length, so the true spoken difficulty is close to grade 8. Product terms (Astro, R2, Codex, Simply Static) raise it for newcomers. #### 👀 Visual learners - Present: live dashboard walkthrough, file listings, a database row appearing, a delete demo. - Improve: no architecture diagram of the three project paths. A one-slide map of static, full-stack, and WordPress-export flows would anchor the chapters. #### 🔊 Aural learners - Present: continuous narration and a spoken recap at 00:13:33. - Improve: a 60-second audio summary of the pricing tiers and beta labels, since numbers are easy to miss when spoken. #### 🗣️ Verbal learners - Present: comparisons to Cloudflare, Vercel, S3, and R2 explain by analogy. - Improve: define "space," "static site," and "full-stack" in one sentence each. The term "S2" (S3) is misspoken in captions and needs correction. #### 🧩 Kinesthetic learners - Present: three concrete builds, each shown running. - Improve: no repo or command list in the description. Add the exact CLI commands and the prompts used so viewers can repeat the tests. #### 🧠 Logical learners - Present: a clear three-case structure and honest reporting of a failed repeat. - Improve: state the success criteria up front (deploys, file count, time) and tabulate results across the three projects. #### 🧑‍🤝‍🧑 Social learners - Present: an invitation to Automattic staff to respond, and to viewers to subscribe and join the newsletter. - Improve: a discussion prompt ("what would you host here?") and a link to the vendor's community channel. #### 🧘‍♀️ Solitary learners - Present: the video is self-contained and chaptered, so it's easy to replay one section. - Improve: add a reflection question, such as "which of your sites could be static?" #### 🌿 Naturalistic learners - Present: none explicit. - Improve: the private-WordPress, public-static approach reduces always-on servers. A sentence on hosting energy would connect to this group. ## 📊 Accessibility assessment #### Screen reader semantics - Present: YouTube supplies the page landmarks, and the 11 chapters give a navigable outline. - Improve: dashboard states (beta labels, a lock icon for unpublished) are shown visually and only sometimes spoken. WCAG 2.2 AA 1.1.1 (Non-text Content) and 1.2.5 (Audio Description, Prerecorded) apply. #### Keyboard navigation - Present: the YouTube player is keyboard operable. - Improve: the video adds no barriers. 2.1.1 and 2.4.7 are met by the platform. The narrator uses a mouse throughout, so keyboard paths in Spacefast itself go untested here. #### Contrast and readability - Present: unverifiable from a transcript. - Improve: small dashboard and terminal text at default resolution risks 1.4.3 (Contrast Minimum). Zoom into UI regions. #### Text resizing and reflow - Present: the player and captions scale independently. - Improve: burned-in UI text can't be resized. 1.4.4 (Resize Text) and 1.4.10 (Reflow) don't apply to baked-in frames. #### Media and captions - Present: auto-captions exist and chapters are set. - Improve: captions garble the vendor ("Automatic"), product ("Space Fast"), builder ("Gentic," "Agility Builder"), storage service ("S2"), and Supabase ("Superbase"). Human-corrected captions would resolve a 1.2.2 (Captions, Prerecorded) shortfall. #### Forms and interactions - Present: none in the video beyond the demo app. - Improve: the demo to-do app's form accessibility isn't shown. WCAG 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value) are worth checking for generated apps. #### Standards reference - Primary gaps against WCAG 2.2 AA: **1.2.2** (caption accuracy on proper nouns), **1.2.5** (visual dashboard states not described), **1.1.1** (icons and beta labels conveyed visually). Caption correction is the cheapest fix. ## 🌍 DEIB assessment #### Cultural breadth - Present: the audience is the WordPress community, and agencies of different sizes appear. - Improve: all examples are English-language, US-priced (dollars) products. Add a multilingual site test, since Polyglots and non-English hosting are central to WordPress. #### Inclusive language - Present: plain, direct second-person address. - Improve: "you don't have a dummy running the ship" near 00:13:33 uses a casual insult. Replace with "once someone experienced is running it" or the concrete condition. #### Neurodiversity support - Present: 11 chapters and a repeated three-project structure. - Improve: the narrator says this was their second recording after a mistake, and some digressions interrupt the flow. A chapter-start summary sentence would help. #### Representation - Present: one narrator, plus a named editor (Eric Karkovack) at the close. - Improve: no outside voice, such as an Automattic engineer or an agency owner, is included. #### Psychological safety - Present: the narrator admits possible user error and frames their failures as feedback. - Improve: invite corrections in the description so viewers with more experience can help without feeling called out. ## ✅ Logical validity #### Strong reasoning - **Direct observation, 00:06:27.** The static site deployed and is shown as files in the project. A claim about what happened, demonstrated on screen. - **Self-limiting caveats, 00:12:50.** "It's not a hosted HTTPS site" is a named confound that bounds the WordPress failure claim. Clarify by testing on a public domain. - **Source-of-inference labeling, 00:05:44.** The WordPress logo on the preview screen is offered as a reason to think Spacefast borrows Automattic infrastructure. The narrator says "tells me," not "proves," which is the right strength. - **Problem framing, 00:10:42.** Static-site movers replace WordPress user management with seat-priced CRMs or self-run auth. The causal chain is plausible and stated with mechanisms. - **Conditional forecast, 00:05:01.** The private-WordPress, public-static benefit is stated as an if-then, dependent on the WordPress path being ironed out. #### Fallacies - **Hasty generalization, 00:12:07.** "It worked once and I couldn't get it to work again" is one person, one localhost site, about seven tries. It supports "unreliable in this setup," not "unreliable." Fix: repeat on a public domain and count successes. - **Unverified comparison, 00:01:26.** The $5 entry price is said to match Cloudflare's Workers plan with no source shown. Fix: link both pricing pages with retrieval dates. - **Inference from a logo, 00:05:44.** The WordPress preview logo is used to infer the hosting backend. Weak evidence, since a shared design asset could explain it. Fix: cite Automattic documentation. - **Appeal to a trend, 00:00:00.** "Lots of people are now moving to static site agentic building" has no numbers. Fix: cite adoption data or say "some agencies I know." - **Undisclosed uncertainty on attribution, 00:12:07.** The Simply Static maintainer claim is qualified with "I believe" and is unverified. Fix: check the plugin's listing before publishing. #### Tone of voice - Curious, informal, and candid about limits. Second person and contractions throughout, with a self-aware line at 00:04:17 admitting a second recording. It hedges often ("could be user error," "not an expert") and pairs enthusiasm about the direction with plain reports of what broke. The close at 00:14:15 shifts to a request for vendor outreach and channel promotion, and the newsletter pitch names the team and editor. ## 🛡️ DARVO analysis Not applicable to this source. DARVO (Deny, Attack, Reverse Victim and Offender) describes a response to accusation or criticism, and this is a product first look with no accuser and no defensive posture. For completeness across the three prongs: **Deny** — nothing is denied; the narrator volunteers failures and possible user error. **Attack** — no critics are attacked; the narrator mentions people who came only "to hate" on Automattic, at 00:00:00, without engaging them. **Reverse victim/offender** — no such move appears. ## 🎯 Conclusion Spacefast, as shown, is an early Automattic entry in simple, agent-friendly static hosting. The static site and full-stack demos worked, with a Codex-built landing page and a MySQL-backed to-do app. The WordPress static export pushed about 1,700 files once, then wouldn't repeat, and the narrator flags localhost as a possible cause. Storage, database, and users are beta, and app-level login was the least clear part. The durable idea is the private-editor, public-static pattern, which reduces cost and exposure if the export is reliable. The unverified parts are the prices, the infrastructure guess from the WordPress logo, the Simply Static ownership detail, and whether the failures are the product or the setup. **Next steps for readers:** if you're an agency, re-run the WordPress export on a public HTTPS domain with 10 deploys and log the failures before promising clients anything. Get prices from the official pricing page. Confirm the real product and builder names, since the auto-captions mangle "Automattic," "Agentic," "S3," and "Supabase." ## 🔄 Refactor Appendix — Spacefast: Automattic’s New Static Hosting (Cloudflare/Vercel Alternative?) > Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad). > Emitted: 5 Literature, 1 Permanent. Resonance filter applied. The price comparisons were dropped as unverified. > > Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Split Pad #### [H1] Spacefast targets teams overwhelmed by Cloudflare > [!quote] [00:00:42] > It looks like a way to compete against the Cloudflares, the Vercels, the static hosting solutions that have dominated the market **Context & use**: - 00:00:42, right after the narrator concludes Spacefast isn't only a site builder. - Keep as the positioning claim. The evidence is the narrator's read of the product, not vendor material. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H2] Spacefast is designed agent-first > [!quote] [00:02:52] > they're definitely leaning into the agent side of this first and foremost. **Context & use**: - 00:02:52, during the dashboard tour showing connected agents and copy-to-agent docs. - Useful for any note on agent-as-primary-user product design. The narrator's evidence is the docs and dashboard, which the narrator describes but doesn't show in full. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H3] Private WordPress plus public static cuts exposure > [!quote] [00:05:01] > Host a WordPress site internally or somewhere on your desktop or on a sort of behind a firewall **Context & use**: - 00:05:01, in the project overview, before the demos. - The narrator ties this to lower cost and lower exposure. Neither is measured in the video. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> #### [H4] Gravatar and wordpress.com could become an identity layer > [!quote] [00:10:00] > the Gravatar and wordpress.com thing is interesting when you start to think of wordpress.com and and Gravatar as the authentication layer **Context & use**: - 00:10:00, after the agent said Spacefast auth wasn't meant for app users. - The narrator treats this as a possibility, not a shipped feature. Note the login options changed between the narrator's builds. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> #### [H5] Static WordPress export succeeded once, then failed > [!quote] [00:12:07] > it worked once and I couldn't get it to work again. **Context & use**: - 00:12:07, after the 1,700-file push, tested on localhost. - One person's early result on a confounded setup. Record it with the localhost caveat at 00:12:50 or the atom misleads. **Tags**: #xref #share <!-- atomicity: 1 idea ✓ --> ### 🧠 Atomic Split Pad #### [P1] Static hosting is only as good as its export path **Claim** (one sentence, Courtney's voice): A platform that promises to host static WordPress is only as useful as its export succeeds repeatedly on a real domain. **Evidence pointer**: [[#H3]] · [[#H5]] **Scope & conditions**: Applies to WordPress-to-static publishing. Doesn't apply to sites built static from the start. The video's evidence is one localhost run, so treat the claim as a test plan, not a finding. **Links**: - [[Static site generation for WordPress]] — because extends - [[Reading vendor demos]] — because contrasts on where the caveat sits, here in the narrator's own account - [[Agency hosting decisions]] — because applies-in client site choices <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Verify Spacefast pricing (free, $5 Go, $15 team) against the official pricing page and record the retrieval date — https://www.youtube.com/watch?v=REtN7aXwBLA #fleeting #inbox - [F2] Check who maintains Simply Static, since the narrator attributes it to an Ollie co-founder "I believe" #fleeting #inbox - [F3] Test the static WordPress export on a public HTTPS domain for 10 deploys and log failures #fleeting #inbox - [F4] Find out whether the wordpress.com login can serve an app's own users, since a Gravatar toggle vanished between builds #fleeting #inbox - [F5] Article seed: "Private WordPress, public static" as an agency pattern, with cost and exposure measured #fleeting #inbox #articleseed ### → Things 3 (max 2 actions) - [ ] Re-test Spacefast static WordPress export on a public HTTPS domain, 10 deploys, and log results — hosting research, 45 min #things - [ ] Verify Spacefast pricing and beta feature list against official pages before citing this video — fact check, 15 min #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Spacefast Automattic’s New Static Hosting.md|Spacefast: Automattic’s New Static Hosting by WP Minute Tutorials]] ## Highlights - [00:00:00] Spacefast. We're about to find out, or at least give you a preview of spacefast.com brought to you by the makers of wordpress.com, Tumblr, Pocket Casts, and so much more. That's Automatic. It's their latest offering into which at first I thought was just a static site builder. And I shouldn't even just say just a static site builder. Lots of people are now moving to static site agentic building processes. Wordpress is certainly in the crosshairs of that movement. Lots of you probably watching this have already moved on and here just to hate on anything Automatic and Wordpress. Let's dive into taking a look at Spacefast, spacefast.com. As I mentioned, a lot of stuff on the home [00:00:42] page here for you to digest. It looks like a way to compete against the Cloudflares, the Vercels, the static hosting solutions that have dominated the market now for the better part of over a decade building out these technologies. The problem with Cloudflare, as much as a lot of people are really enjoying that stack, is its infrastructure. It's big, mature infrastructure. When I think of Cloudflare, I think it's second to something like an Amazon Cloud or a Google Cloud where there is just a gazillion things happening in it. And if you're just not seasoned in infrastructure, well, now you're challenged with just figuring it all out. Spacefast looks to be the answer. Looks like they're dumbing down the ([View Highlight](https://read.readwise.io/read/01m3psgdch25x4cc1drszws5t6)) - Note: [H1] Spacefast targets teams overwhelmed by Cloudflare - Tags: atom/literature/h1 - [00:02:52] I have three mini projects. I'm calling this a preview video. This is not a deep dive video because I'm not an expert on Spacefast. Yeah, plus I think it's still pretty early days for things to get totally up and running. Very easy, clean, easy interface, dashboard's easy, there's nothing complicated. Spaces is to projects, right? You have a project, it's a space, that's what they call it. A few different things that can happen is you can track and see what your agents are doing, which agents are connected, what's happening with agents across the board. And they're definitely leaning into the agent side of this first and foremost. You'll see it in like every piece of documentation, everything that you're touching, it's like, "Hey, don't even want to read this, copy and paste this [00:03:34] and give it to your agent." Like they know that everything is just let me dump this off to the agent and have the agent do it. So, they're doing a great job with that. There's a set of connection connectors which is I mean, I don't want to say fairly limited, it's it's limited to like the big players, Google, CloudFlare, even. Um And you can connect up your Spacefast account to do the different things that these different services offer. So, connectors, I'm I'm sure they'll have a lot more as time goes on. Webhooks, of course, your account variables, if you need to store uh variables and secrets, um you can push from a Git repo, you can drop a file, set of files here, and then just go ahead and create a space and ([View Highlight](https://read.readwise.io/read/01m3psgg8v569831c0q5z9gxv2)) - Note: [H2] Spacefast is designed agent-first - Tags: atom/literature/h2 - [00:04:17] start uh working with your thing. So, I think that's the ease of use that they're trying to do. Every time, this is the second run through I've done of this uh of this uh recording because I I messed something up before. Whenever I go into either the drop or push screen, I'm not sure what it is, it creates this new space. Now we have four spaces. We started with three. Uh that's all that matters to me. So, let's go ahead and delete this just to show you how to delete a space. So, now that space will be gone. The design stuff is still kind of quirky, like I think it's kind of cool, but also like these sort of hand-drawn icons kind of get like at first I was like, "What is that?" It's a lock, right? This is not published basically to to the web. [00:05:01] Three projects, we have a WordPress site, we have a full-stack app, and we have a static site because that's what you can host with Spacefast. You can do the static site like I've built, and I'll show you in a second. You can do a full-stack app, which I'll show you. And of course, you can do a static WordPress site, which I had a lot of issues with, but it does work. I'll kind of go through that, and I think like when that is all ironed out, this is what a lot of folks are be are going to be looking for. Host a WordPress site internally or somewhere on your desktop or on a sort of behind a firewall, and then publish your static site to Spacefast to not only decrease the cost, but decrease the ([View Highlight](https://read.readwise.io/read/01m3psgjrvmrjp8136xdaf6pyj)) - Note: [H3] Private WordPress plus public static cuts exposure - Tags: atom/literature/h3 - [00:10:00] the authentication for that app, like basically add a new user, user gets the email, or the magic link, and they can sign in. It said it couldn't do that. It couldn't replace that. It wasn't meant for that. It was meant for users logging in to Spacefast. I don't know if the agent knew all of it off the top of its head. Can I say that? It didn't work. I could register a Google app and connect that up to this, and presumably I could have a Google sign-on to this app, but the Gravatar and wordpress.com thing is interesting when you start to think of wordpress.com and and Gravatar as the authentication layer, which I think I feel like they've been trying for that forever with Gravatar, and and this might be the thing that Gravatar [00:10:42] shoehorns in. But again, presumably you you could have your user authentication and management here, which is pretty big, because that's what WordPress provides, which is like totally overlooked and undersold when it comes to building stuff with WordPress, especially those people who are moving off to static sites, and either getting some kind of third-party CRM back-end, which charges by user seats, or just has weird permission structure, or you then go to that infrastructure layer, which is something like a Superbase, and now you're kind of, you know, rolling your own authentication. Of course, they handle it, but now it's just like another infrastructure thing that you're managing, whereas WordPress has it built in. But Spacefast understands that, and they have ([View Highlight](https://read.readwise.io/read/01m3psgne4aqezm2gdyfxngv5s)) - Note: [H4] Gravatar and wordpress.com could become an identity layer - Tags: atom/literature/h3 - [00:11:25] uh users, which will eventually be a lot easier to use. Third case is WordPress static hosting. Now, this is the one where I had the the most issues and I just don't know if it's ready for prime time yet. So, I'm in the Studio app. This is what I use to build this example site. Uh this is another experiment. You can see some other videos that I've made about Studio, but they now have a Gentic building uh connected up to wordpress.com where you buy credits from and it's uh Automattic's Gentic play at at building websites and I built this example WordPress agency site locally on Studio, but that's not the uh that's not the lesson here. The lesson is is I [00:12:07] installed the Space Fast plugin, which also installs the Simply Static plugin, which is a third-party plugin by one of the co-founders of uh Ollie theme, I believe. I'm interested to see how long they continue to recommend this plugin, if not buy this plugin perhaps or fork it all into the Space Fast plugin. And I was able to deploy it once and it took forever. It pushed every file of WordPress up to Space Fast, uh which you can see down here. It's got 1,700 files inside of Space Fast. I've never done static front-end WordPress before, so I don't know if that's the nature of the beast when it comes to deploying to the front end, but it worked once and I couldn't get it to work again. Here's ([View Highlight](https://read.readwise.io/read/01m3psgr344ch15rwcehe65n2f)) - Note: [H5] Static WordPress export succeeded once, then failed - Tags: atom/literature/h3