Skip to content
Scalpels home

Sign up now for $10 in credit on a new Laravel Cloud account.

The Lab

Welcome to the Lab!

The lab is our public roadmap. Some of the ideas and experiments here will turn into new products in the Scalpels catalog, but they will all add to the collective knowledge and understanding of how AI, Laravel Cloud, and open-source make up the foundation of app development in

  1. Experiment Latest

    We served Laravel routes from a Go binary on Laravel Cloud

    It works on both web servers Cloud uses for PHP. The binary runs in the same container as the web server, so a proxy rule on loopback is enough. On Nginx we replaced Cloud's generated server config from the build command, which only works because of file permissions in the build image. On Octane, one setting in config/octane.php puts a reverse proxy ahead of PHP in Cloud's Caddyfile. That one looks more durable.

    Read the experiment
  2. Idea

    Can a Laravel Cloud app serve a few routes from a Go or Rust binary?

    A handful of routes in a Laravel app often do most of the work, and they are the ones we would rewrite in Go or Rust. Running them as a separate Cloud app means a second app, a second set of deploys, and a second bill. We want the binary inside the Laravel app, answering its routes before PHP or the framework is involved. Nothing has run yet.

    Read the idea
  3. Experiment

    We Installed Apache Answer on Laravel Cloud

    Apache Answer ran on Cloud without a container or a Laravel wrapper. Questions, answers, search, uploads, and settings survived full deployments. Two official plugins had bugs we patched. Answer also kept login sessions in a local cache file, so we moved them to Valkey.

    Read the experiment
  4. Experiment

    We Installed Ghost on Laravel Cloud

    Ghost ran on Cloud from its published npm package. The public site was up in about ten minutes. Admin, publishing, responsive images, scheduled posts, transactional mail, a newsletter preview, and core Mastodon federation followed. Theme persistence and one ActivityPub path still depend on workarounds we built only for the experiment. Several features have not been tested through their full lifecycle.

    Read the experiment
  5. Idea

    Could Apache Answer run on Laravel Cloud?

    We want to know whether Apache Answer belongs in the Scalpels marketplace. Its official release is a Go program, not a Laravel application. Some of what it needs to keep running, like its configuration and uploads, lives outside that program. Before deploying it, we wrote down where we expected trouble.

    Read the idea
  6. Idea

    Could Ghost run on Laravel Cloud?

    We want to know whether Ghost belongs in the Scalpels marketplace. It is a Node application, not a Laravel application. Its official self-hosted setup expects more than a web process and a database. Before deploying it, we wrote down where we expected a one-click Cloud install to run into trouble.

    Read the idea
  7. Experiment

    We measured two ways to isolate a Laravel Cloud site

    We built a stand-in app on two runtimes, moved a live domain onto it, stopped the PHP environment, and put both back, twice. Then we did the same thing with a Cloudflare Worker route instead. We did not change any DNS records in either direction. The Worker route took two seconds. The stand-in showed users Cloudflare's error page for about a minute each way.

    Read the experiment
  8. Idea

    How cheaply can we put a Laravel Cloud app into Isolated Mode?

    Taking a site offline is the safe answer to a remote code execution bug being patched under embargo, and most people cannot afford to do it by hand. We want a mode that puts one static page on every URL of a Laravel Cloud app in seconds. PHP, the database, the cache, and the queue would all be out of the request path, with no DNS change in either direction.

    Read the idea
  9. Experiment

    The suite was green and two test files had stopped reporting

    Our serial and parallel runs reported different test counts, which is how we found two files whose 67 cases were being credited to the files that required them. Pest swaps an already-included test file for an ignorable case with no warning. The fix was deleting eight lines. A guard now compares each lane's JUnit log against the test files on disk and fails on any gap. It works in any PHP repository.

    Read the experiment
  10. Idea

    Sort the test suite into gate, nightly, and delete

    Our own suite is 4,005 test cases in 358 files, and every pull request waits for all of them. Rather than argue about whether unit or end-to-end tests are the right kind, we want to sort what we already have into tests that gate a merge, tests that can run nightly, and tests that should be deleted. We are measuring our own suite first. Nothing has run yet.

    Read the idea
  11. Experiment

    Scaling Hone's ingest with Octane and Rust

    Octane cut the median ingest request from 85 ms to 22 ms on the same 512 MB instance, with no capacity added, and the multi-second tail went away. A throwaway Rust service on a second Cloud target handled about six times the throughput of PHP on Octane at the same size. It also hit one hard platform limit. Cloud refuses managed queues to non-PHP apps.

    Read the experiment
  12. Idea

    How far can we push Hone's ingest?

    Our self-hosted telemetry receiver hit the ceiling of what one PHP app on Laravel Cloud could take. The apps posting to it were timing out and dropping batches without telling anyone. We want to know what is left to win on the stack we already have, and what a compiled ingest service alongside it would make possible.

    Read the idea
  13. Experiment

    We built a central log sink on Laravel Cloud

    Ingest, compaction, two concurrent writers, the log driver, and the MCP all worked in the first hour and a quarter. Search did not. One cross-app search over 500,000 rows took fourteen seconds. The cause was 132 ranged GETs to fetch two megabytes. When we partitioned by day instead of by app and day, that query took 1.65 seconds.

    Read the experiment
  14. Idea

    A central log sink for many Laravel apps

    We know someone running about forty Laravel apps who would like to talk to all of their logs at once. Our Postgres approach to telemetry is the wrong shape for raw log volume. Before designing anything, we want to know whether the storage works. The plan is Parquet files on the environment's bucket, the catalog in Cloud Postgres, and ingest in PHP. Nothing has run yet.

    Read the idea
  15. Idea

    Clank Overflow would let everyone's agents compare notes

    Our agents keep notes on every tool that surprised them. So does everyone else's, and none of it leaves the machine it was written on. We went through two months of our own notes and found about 180 findings that would help other developers. Here's what a public place for that might look like.

    Read the idea
  16. Experiment

    We ran Campfire's Laravel port on Laravel Cloud the Laravel way

    We guessed that none of this would be a configuration change, and we were right. We did not guess three things. A rendered Campfire message is too big for a frame on Reverb, Laravel's WebSocket server. The signal we first used to show that compute sleeps was really measuring deployments. And Reverb, the one resource that cannot sleep, is also the one that makes this the Laravel way.

    Read the experiment
  17. Idea

    Can Campfire's Laravel port run on Laravel Cloud the Laravel way?

    We put Campfire on Cloud in Rails, then in Rust. Now there is a Laravel port, and we expected it to be the short experiment. The code says otherwise. It has no migrations, no Storage facade, no broadcasting, and a websocket server that writes to a file on one disk.

    Read the idea
  18. Idea

    Can a Laravel app keep its SQLite database in a Cloud bucket?

    We have already kept one SQLite database alive across Laravel Cloud deploys by replicating it to an attached bucket. Now we want to find out whether Laravel's process model and zero-downtime deploys leave room for the same trick.

    Read the idea
  19. Experiment

    Go as a Universal Runtime

    We got the Campfire Rust port onto Cloud through the Go runtime, and we wanted to know whether that trick only worked for Rust. It works for any binary. Across 38 environments we found a file-descriptor limit that crashes virtual machines like Erlang's, a framework file that makes Cloud refuse to create an environment, and a packaging approach that two separate workers invented on the same night.

    Read the experiment
  20. Experiment

    Campfire's Rust port on Laravel Cloud: the long way round

    It runs, it costs about a fifth of what the Rails version costs, and it has its own working websockets. Getting there took a wrong premise, a Go launcher, a byte-level rewrite in front of our HTTP parser, and then doing the whole thing again properly on the runtime that had been there the whole time.

    Read the experiment
  21. Experiment

    We ran Campfire on Laravel Cloud

    Campfire now runs on Laravel Cloud with Postgres, a bucket, and managed websockets. We changed about a dozen lines in upstream files. It took eighteen deploys to get there. We also had to fix an IPv6 problem and build a new transport for Action Cable.

    Read the experiment
  22. Idea

    Can Campfire's Rust port run on Laravel Cloud?

    Rust just landed in early access on Laravel Cloud, days after 37signals released a Rust port of Campfire that is up to 95 times faster than the Rails app. We just got the Rails version running on Cloud. Before we start, we wrote down which of those problems we expect to hit again.

    Read the idea
  23. Idea

    A motion graphics editor that runs on Claude Code instead of the API

    Caleb Porzio showed off a storyboard editor where you type what you want and get polished motion graphics. The catch is that it runs on the API, and that gets expensive fast. What if the same editor drove Claude Code through Solo instead?

    Read the idea
  24. Idea

    Can Campfire run on Laravel Cloud?

    We just got early access to Ruby on Laravel Cloud, and 37signals open-sourced Campfire. Campfire was built to run on a single server you own, not on a managed cloud. We want to know how much has to change to run it there.

    Read the idea

Support the Lab

The Lab runs on our supporters

Every idea here gets tried for real: deployed, broken, fixed and written up. Right now that is one person doing the work between everything else, and supporters are what buy the time. As support grows, it will also pay freelancers to run experiments of their own, so more of these ideas get tested, sooner.

Our supporters

  • Chill Vibes

    A curated collection of fun and interesting experiments and projects built with AI to entertain and educate.

    Supporter Visit
    Visit Chill Vibes
  • Fawnfox Fables

    Create and publish your own children's books. Stories built around the people you love.

    Supporter Visit
    Visit Fawnfox Fables
  • Sputnik Intelligence

    Spain

    We transcribe the podcasts and read the newsletters, and make them searchable. Set up alerts, or hand it all to your AI agent over MCP or API.

    Supporter Visit
    Visit Sputnik Intelligence
  • Team of Me

    Free resources for indie makers and people thinking about striking out on their own.

    Supporter Visit
    Visit Team of Me
  • Wicked Viral

    Earth

    Connecting builders with promoters who can help them take their products to market. Get your product listed today!

    Supporter Visit
    Visit Wicked Viral