Matt: The Spacefast Story

Make it with Spacefast

Weekend is starting, Anthropic has IPO’d, and it’s time to vibe code. Yes, the WordPress guy is launching something where you never have to see a wp-admin dashboard (unless you want to). 🙂

Like all great products, Spacefast launched with a manifesto from its founder, Batuhan İçöz:

People who never thought of themselves as builders are making software. They’re making presentations, games, websites, and little tools for themselves and their work. HTML is quickly becoming the new PowerPoint, agent-made dashboards are replacing a whole category of business intelligence tools, ease of managing everything with code is removing the need for CMS for many sites. We are speeding into a world where describing your favorite to-do app and seeing it come to life is going to be easier and faster than finding the perfect app for you.

Please read the whole thing! I’ve had so much fun working with Batu this year and seeing this little nugget of an idea get more and more ambitious.

A good way to try out Spacefast is to wait until your AI makes an artifact for you, then tell it:

Put this on Spacefast.com and send me the link.

Or if you want to be fancy, point it to https://spacefast.com/setup.md. If you think your AI is cool now, wait until you give it a real database! One we’ve scaled to billions of rows and trillions of queries over the decades.

Any agent can publish something there for 33.3 hours, a time period we randomly picked with no significance whatsoever. If you want something to stay up longer, you can register with your email, WordPress.com, Google, or X account. I believe the future is much more “bring your own model”/BYOM than trying to outpace the progress of the frontier labs.

Spacefast features: shareable links, private sharing, version history, on-page comments, a database, file uploads, and stats.

The free tier is absurdly generous for early adopters: 20 Spaces, 20 custom domains, a million dynamic requests and a terabyte of cached traffic a month, commercial use allowed, no credit card, and no surprise bills. At $5/mo you unlock more Spaces, hourly database backups, and your pick of datacenter, and at $15/mo, teams.

Play With It!

I’ve found Spacefast useful for having my Claude and Codex work on the same artifact, for sharing within Automattic using the teams feature without worrying about leaking proprietary data, for spinning up silly games or apps on a whim, and for giving my friends who (rightly!) enjoy using Replit, Lovable, or Cloudflare another place they can point their agent to that might be less expensive, might give them some more forward compatibility with Open Source and no vendor lock-in, and might unlock superpowers for them in the future.

One of my goals behind the Radical Speed Month experiment, where about a third of the company split into teams of one to three and worked on whatever they felt most called to, was to give people a chance to express their creativity and drive outside of the normal framework of Automattic’s products and processes. It was the beginning of this new version of Automattic, experimenting our way into the future of work again, and Spacefast came out of it.

There’s a lot more to the story of how you make an environment where something like Spacefast can be created inside of an existing company, how founder energy can really seem dissonant inside a bigger corporation but is actually critical for survival, and how to protect successful experiments from helpful smothering, but I’ll save that for another day. Right now I want to just give kudos to the launch team of Artur Piszek, Batuhan İçöz, Eduardo Villuendas, Fatih Kadir Akın, James Rutherford, and Stefano Sala for embodying the Automattic Creed and writing a new chapter in the book of WordPress. It’s a small team, but Spacefast gets superpowers from across Automattic. You can geek out with the team on Discord about the super-creative ways they use WP Cloud and all the infrastructure we’ve built.

Choose Freedom

Just as when humans gain wisdom they grok and choose Open Source whenever they can, as agents gain intelligence, I believe they’ll find the Freedom and Agency an Open Source foundation can provide, with battle-tested, secure, and scalable primitives, to be irresistible. And I think if you spend your money with companies that support freedom-expanding rather than freedom-restricting licenses, our future will be a lot brighter.

It’s so fun to be making software right now! Between the intelligence jumps of the frontier and the optimizations making local and private inference so useful, there’s a world of possibilities opening up.

Across Automattic we have teams shipping like never before. On something new like Spacefast, they’ll commit to something crazy like 30 days of new features. On the Open Source projects we contribute to, it shows up as the Core Security Initiative closing nearly 3,000 reports in a year when WordPress received more of them than in the previous 12 years combined, which is the tip of the iceberg for what’s been going on across the millions of WordPresses and customers we support.

The Backstory

You thought this story started in April 2026 with Radical Speed Month, but it actually starts in 2010! Elif Batuman wrote “The Memory Kitchen” for The New Yorker about a chef, Musa Dağdeviren, bringing ancient recipes and ingredients back to life, and her words entranced me so much I knew I had to visit his restaurant in Istanbul.

Cooks in white hats and striped aprons serve customers from rows of pots at Çiya's busy counter in Istanbul.
Musa Dağdeviren (right) in the kitchen at his restaurant Çiya Sofrasi. Photograph by Carolyn Drake

Trough my contact form I got the best cold pitch I’ve ever gotten, from travel wizard Darin Jensen, about how cool Turkey was, so my friend Tim Ferriss and I decided to have another adventure.

Tim Ferriss with a buzz cut and a video-game T-shirt in a crowded Istanbul market street.
One of the last times we both got haircuts together

We both spoke at WordCamp Turkey in Istanbul, and during my Q&A I got a question from a kid whose name you’ll recognize:

Batuhan İçöz: Seven years ago, you created WordPress as blogging software. Today, a lot of users use WordPress as content management software. How do you define WordPress? Is it blogging software or content management software?

Ma.tt Mullenweg: I guess a deeper question would be, how do I define content management software? Historically, CMSs have meant software that’s really hard to use, sucks, and has the whole kitchen sink thrown in. It’s got 50 screens, makes 80 database tables, and does really, really complex things. The idea is that it does everything, so people will choose it. In reality, it ends up doing nothing well, a jack of all trades, master of none.

How I think of WordPress is shifting that a little bit. I sometimes refer to WordPress as a content management kernel, much in the same way an operating system has a kernel. WordPress is in the very middle. We want to be small, light, fast, easy to use, and, most importantly, modular.

So the idea is that there are 10,000 plugins available to do the kitchen sink. Whatever weird thing you want to do on your site, you can pick the plugin that enables you to do that. The beauty of that is that we don’t have to build all those features in. WordPress doesn’t need to get super bloated to have as many users as we do. We can keep the core really small and have plugins that serve the needs of different communities. There’s a plugin to turn it into a store for e-commerce. There’s a plugin to do collaborative editing of a book. It’ll do pretty much anything you can imagine, and most things you wouldn’t imagine.

That is the vision of WordPress, and also why it’s been successful.

What a prescient question! Batuhan had come to WordCamp because he followed a lot of the people there on Bret Taylor’s FriendFeed, basically an early fediverse-like aggregator.

Tim and I ended up hanging out with a few WordCampers after the conference, and adorably there’s a picture of Batu and me in my 2010 photoblog.

Matt Mullenweg and Batuhan İçöz in a park in Istanbul.
Me in Thomas Pink, Batu in an awesome Def Jam t-shirt

A few weeks later he turned 15. A few months after that, he bought the $15/yr Custom CSS upgrade on WordPress.com and posted about Code is Poetry on Quora. Thirteen years later, he’d join Automattic when we acquired Kishan Bagaria’s company, Texts.com. Three years after that, he’d turn a month-long hackathon project into a movement to reinvent the core principles and freedoms of WordPress for a new generation with Spacefast. Wow

See also: Obi Felten on putting Spacefast to work, Rob Pugh on becoming a better developer, Jordan Gillman on shipping his every whim, Jen McFadden on building her family a task manager, and Jamie Marsland on avoiding the next generation of lock-in.

 

WordPress.org blog: Global Partners Across the Third Quarter of the 2026

From July through September 2026, the WordPress Community organized 39 events with the financial support of the project’s five Global Partners: Jetpack, WordPress.com, WooCommerce, Bluehost, and Hostinger. From a small gathering of 56 in Mannheim to a Contributor Day in the Philippines that drew 322 people, and the first-ever WordCamp in Eket, Nigeria, these events brought newcomers, contributors, and builders together around the world. The 39 events were too many to cover in one post, so this recap highlights a few of the moments that stood out.

Events around the world

The quarter opened in July with WordCamp Mannheim, a small event with real range. The 56 attendees covered topics from AI and WordPress block development to current security know-how, along with presentations on values, training, and the open web.

In August, the momentum moved to Nigeria, where Eket held its inaugural WordCamp on August 15 under the theme “From Idea to Income: Building Opportunities with WordPress.” Engr. Aniebiet Udoh took the stage for the keynote, challenging attendees to embrace the global reach of the web: “The internet has no small towns.” He urged creators to follow a five-step path:

  1. Notice a local pain
  2. Solve for one person
  3. Validate with real use
  4. Standardize the repeatable core
  5. Scale to global markets

Later in August, WordCamp Philippines drew approximately 434 attendees, contributors and first-time attendees, to Iloilo City on August 28-29.

One of the highlights of Contributor Day was the Open Source Library, an activity inspired by the Human Library concept. Instead of borrowing a book, participants could “borrow” a person and spend time having a meaningful conversation about their experiences, careers, communities, and journeys in open source.

WordPress.com ran both a booth and a dedicated Community + Education table. The education table alone generated connections with 14 schools and universities, sparked three new meetup applications, and produced a new Campus Connect application from Colegio San Agustin in Bacolod.

Students and first-timers in Uganda

In Uganda, WordPress is reaching people who have never worked with it before. The third edition of WordCamp Masaka welcomed students and first-timers to participate in a hands-on WordPress Practical session. Led by community members, Stephen Dumba and Cinderella Mbabazi, Florence Namyalo, the Founder and CEO of RAPCIO, and the IT team of Equator University of Science and Technology, the group installed WordPress, explored the dashboard, and began building websites.

In September, nearly half of this year’s participants at WordCamp Jinja were students. One of them, fascinated by the WordPress ecosystem and its spirit of generosity and inclusivity, drew all the sponsor logos by hand so he could remember them after the event.

From classrooms to community

In September, WordCamp Costa Rica brought together 327 people. A noteworthy highlight was the pre-event WordPress Studio workshop, where 25 participants each built and launched a live site on WordPress.com in a single morning.

The event also demonstrated the growing pipeline from education to community. At least 100 attendees came to WordCamp Costa Rica after first experiencing WordPress through WordPress Campus Connect events at Beenova and UCR Esparza earlier in the year.

The thread running through many of these stories is education and the increasing attendance by students who have been exposed  to WordPress through the WordPress Campus Connect event series. These events serve as a pathway for the next generation of WordPress contributors, builders, and professionals, and each stop this quarter added to that pipeline.

What’s next

The current cycle of the Global Partnership Program continues through March of 2027, with WordCamps scheduled in Guatemala, Belo Horizonte, Bandung, and beyond. WordPress Campus Connect events are expanding across Latin America, Southeast Asia, and Africa. Thank you to Jetpack, WordPress.com, WooCommerce, Bluehost, and Hostinger for making this quarter possible, and to every organizer, volunteer, speaker, and attendee who brought these events to life.

To learn more about WordPress community events near you, visit events.wordpress.org.

 

Akismet: Introducing the official Akismet JavaScript SDK

Spam doesn’t care what your site runs on. A contact form on a Next.js app or a comment box on a Cloudflare Worker gets the same junk a WordPress blog does. After the PHP SDK in June, we’re excited to release the official JavaScript SDK for Akismet.

Who is this for?

@automattic/akismet is a TypeScript client for the Akismet API. It’s for developers adding spam protection to comments, contact forms, or signups in a JavaScript backend.

  • It covers the whole Akismet API.
  • It runs on Node.js 22 and later, and on Bun, Deno, and Cloudflare Workers.
  • It comes with typechecked examples for Express, Fastify, Hono, Next.js, and plain node:http.

A two-minute quick start

npm install @automattic/akismet

Then check each submission in the route that receives it. In a Next.js app, that’s app/api/comments/route.ts:

import {
  Akismet, AkismetError, ContentType, SpamVerdict,
} from '@automattic/akismet';

const akismet = new Akismet({
  apiKey: process.env.AKISMET_API_KEY!,
  site: 'https://your-site.com',
  isTest: process.env.AKISMET_TEST_MODE === '1', // Disable learning
});

export async function POST(request: Request) {
  const { comment, name, email } = await request.json();
  try {
    const result = await akismet
      .forRequest(request, { trustedProxyHops: 1 })
      .check({
        body: comment,
        authorName: name,
        authorEmail: email,
        type: ContentType.Comment,
      });
    console.log(result.verdict);
    if (result.verdict === SpamVerdict.Discard) {
      // Akismet is sure it's spam. Drop it.
    } else if (result.isSpam) {
      // Hold it for moderation.
    } else {
      // Publish it.
    }
  } catch (error) {
    if (!(error instanceof AkismetError)) throw error;
    // Safe to log: the SDK redacts the API key.
    console.error(error);
    // Akismet failed or rejected the input. Hold it for review.
  }
  return new Response(null, { status: 202 });
}

site is the front page of your site. Check out the README for details on how the the Client IP is configured.

Every framework follows the same flow: check the submission, then act on the verdict. You can check out some examples for Express, Fastify, Hono, node:http, and Next.js Server Actions.

What’s in 1.0

  • Spammers can’t fake their IP. Trust only the headers from proxies you allow.
  • Your API key stays out of your logs. Log every error worry free.
  • You can tell Akismet when it gets one wrong. Keep the content you checked and its verdict, when a moderator finds missed spam or a false positive, report it. Akismet learns from those reports, check out the README for how.

Get started

The Akismet SDK is open source under the MIT license.

  • Find it on npm.
  • Read the code and docs on GitHub.
  • Building with an AI coding agent? Tell it to read the SKILL.md that ships with @automattic/akismet.

You’ll need an Akismet API key. The Personal plan is name-your-price for personal sites and blogs, and commercial sites need a paid plan sized to their traffic. Your code stays the same whichever plan you’re on.

Found a bug, or something that doesn’t fit your stack? Open an issue on GitHub.

 

WordPress.org blog: WordPress Credits Boost Translation

Contributors to the Costa Rican Spanish locale are making WordPress more accessible to Spanish-speaking communities in Costa Rica. Students from local schools and universities have joined the Polyglots team, helping translate WordPress.org projects and review community contributions.

Students from two universities and a bilingual high school in Costa Rica contributed through the WordPress Credits program, which lets students earn academic credit for contributing to WordPress as part of their studies. On the Polyglots team, contributors suggest translations for WordPress Core, plugins, themes, and WordPress.org sites. Locale editors review and approve those suggestions.

Between September 2025 and November 2026, translation coverage in es_CR rose from 38% to 100% on WordPress.org, from 39% to 98% in the Plugin Directory, and from 45% to 99% in the Forums. WordPress Core reached 99%, while the queue of strings waiting for review fell from 665 to 105.

One participating school, Liceo Experimental Bilingüe José Figueres Ferrer in Cartago, was the first high school in the Americas to implement WordPress Credits through its Student Community Service program, Trabajo Comunal Estudiantil. Its students focused on Polyglots and helped advance the es_CR translations.

WP Credits pushed me to contribute to something real, not just a class assignment. Going from not knowing what a ‘string’ was to translating hundreds of them was a great feeling, and it showed me that even a ‘small’ contribution like translation genuinely helps people who use WordPress in Spanish every day.

Lester Matarrita Rodríguez, Fidélitas, May 2026

The project also produced a resource for new contributors. The video “Cómo contribuir en el equipo de traducción” walks viewers through contributing on the WordPress translation platform, using Costa Rican Spanish as an example.

If you read and write a language other than English, you can help make WordPress more useful to people in your language. Start with the first steps in the Polyglots Handbook to learn how to suggest translations and take part in the review process. Then check the translation stats page to find projects that need work in your locale. Educators can explore the WordPress Credits program to learn how students can contribute to WordPress as part of their studies.

 

Matt: TLD Ideas

.jazz — Obviously reach out to the top musicians and see if they’d like their first name, and direct a percentage of profits toward music education. Programs like Summer Jazz Workshop were a huge part of me becoming who I am today. Premium registration and renewal pricing like .blog.

.php — Not sure about the commercial appeal of this but can definitely do a Five for the Future, or maybe Fifty for the Future, towards PHP Foundation. I could see .php being kind of a punk web creator brand. PHP in my head is a very hackable, easy way to build web things, though recent versions have gotten more Java-like. (And will programming languages matter anymore?)

.soul — I think just a standard premium pricing model, but maybe a minimum registration of 5 years or more, perhaps closed to humans, with agent-only registration: a place they can store themselves.

.tumblr — Would be nice to give everyone a domain instead of a subdomain or directory address.

.woo — Could be fun as the web equivalent of getting a booth at the farmers market to sell things.

.wordpress — Could go two directions, either lean into the name being a place for well-curated and secured open source, official and vetted resources, or go like .tumblr and let everyone have one. For the latter, since everyone has copied all our primitives, I think we need to introduce some new ones to make a WordPress different from any other CMS.

.matt — The interest in this surprised me. It turns out there’s a whole social media subculture of “name” handles. Maybe a very high price like $111/yr, paired with some of the matt.* domains I own—perhaps an auction to be the top Matt at matt.dentist or matt.accountant, with the idea that you’d pass the domain on to another Matt when you retire. There are millions of Matts and Matthews in the world, so the TAM is bigger than you would expect. I’ve been discussing this with the secret matt-cabal on the .org Slack. I need to be careful or I’ll start another matt.company.

 

Donncha: Photo Competition Manager 0.4.0

This WordPress plugin, Photo Competition Manager, is for photography clubs that want to run photography competitions. It allows members to upload photos and then vote on each, displaying them in a slideshow if the images are to be projected. Voting is done through a mobile interface. Results are shown immediately.

This version is a significant upgrade but many of the changes are not visible to the end user. The backend was ripped apart and improved so it runs better. Various bugs were squashed, but two major features were added as well:

  1. External judges can judge the photos rather than asking the members to vote. A panel of judges is created and can be individually added to a competition. They are emailed (or given) a link to judge and use a similar interface to the mobile voting interface used previously.
  2. I added support for interclub competitions which adds more conditions to the competition. It’s currently based on the SACC interclub competition rules (X+2 substitute images, maximum Y images per photographer) but I expect we’ll add to that in the future.

A typical workflow would consist of:

  1. Decide if you’re going to ask your members to vote or use external judges. If it’s judges, then set them up with their email addresses on the Judges page.
  2. Set up the required pages on the Setup Wizard page. Those are voting and results pages.
  3. Create a competition. I would set the start date to 1 or 2 weeks before the judging night, and set the close date to the day after judging night.
  4. You will already have added the members of your club through the Members page, so with uploads open, send them the upload link.
  5. Hopefully uploaded images will start appearing over the next few days.
  6. On judging night, the Voting Controls page is used to close uploads, display the slideshow (optional if it’s a print competition) and open voting.
  7. The Voting Controls page will show a QR code for the voting page if you’re using the password system. Voting by members this way is an honour system. They enter their name, the password and then rate each photo as it is displayed on the slideshow. There is also a voting link system where a link is sent to each member.
  8. Voting is closed. If desired, a critique slideshow can be done next, and then we move on to the next category.
  9. When the competition is done, click on the “Show Results” button and then the Results page to display the results to the members.
  10. On the dashboard Results page, there’s a button to email the members their individual scores. A CSV of the results is also available on this page.

I’ve run several test competitions using the development site I use here, but I welcome bug reports. The 0.3.0 version was used by Blarney Photography Club for the last year and worked with minimum problems, but I spent a lot of time on this version in the last 2 months so the more eyes on it the better.

If you don’t have a WordPress site, I can recommend WordPress.com. The personal plan there is currently €4/month and lets you run plugins. I work for Automattic, who run WordPress.com, so of course I’d recommend them. 🙂

#PhotoCompetitionManager #Photography #WordPress #WordPressplugin 

WordPress.org blog: WordPress 7.1.5 Release

This security release features fixes for multiple issues.

Because this is a security release, it is recommended that you update your sites immediately.

You can download WordPress 7.1.5 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically.

WordPress 7.1.5 is a short-cycle release. The next major release will be version 7.2, currently planned for December 8th.

For more information, please visit the WordPress 7.1.5 HelpHub site.

Security updates included in this release

  • A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
  • A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
  • A reflected XSS in the legacy media library popup, reported by Anthropic.
  • An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
  • SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
  • Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
  • Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
  • SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
  • Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
  • Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
  • Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
  • Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
  • Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
  • Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
  • Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
  • A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
  • Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
  • Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
  • XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
  • Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.

Thank you to these WordPress contributors

This release was led by Jeremy Felt, Jerry Jones, and Jarda Snajdr. WordPress 7.1.5 would not have been possible without the contributions of the following people:

Aaron Jorbin, Adam Silverstein, Alex Concha, Andrew Duthie, Andrew Serong, Ben Bidner, Christiaan Swiers, Daniel Rodriguez, Dennis Snell, Ehtisham Siddiqui, George Mamadashvili, Giovanni Cintolo, Greg Ziółkowski, Isabel Brison, Jarda Snajdr, Jeremy Felt, jeryj, Jesse McNeil, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Juliette Reinders Folmer, Kira Schroder, Lance Willett, Logan Homolka, Luca Tumedei, luisherranz, Marc Montpas, Marin Atanasov, Mohammad Jangda, Nik Tsekouras, Peter Wilson, Rafie Muhammad, ramonopoly, Rudy Faile, Sergey Biryukov, Shu Takahashi, Weston Ruter

Backports

As a courtesy, the security fixes were backported to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready.

In WordPress 7.0, 1024 bit certificates were removed from bundled root certificates. This change has been applied to 6.9.12 and earlier as part of this release.

WordPress 7.2 RC 2 has also been released, containing all applicable fixes.