Introduction

Goribu is the full-stack React framework on Cloudflare Workers. It exists to provide a more direct way to build web apps that feel good to code and work with. Server-first, fast to change, easy to reason about and without the need to over-optimize before the product has even found its shape.

It tries to avoid complexity like client-side caches, app-wide cache mutations, loaders, separate API layers, adapters and runtime glue code stitching together a bunch of different services. Sometimes these are necessary but most of the time they slow down the ability to change your mind, add new features and move fast.

The Happy Path

Goribu chooses a different road. The patterns that make this work are deliberately uncomplicated and have been around for years. Routes are files that hold their page and the handlers that feed it side by side. There is no separate API layer by default, because the handler that renders a page on first load is the same one that answers in-app navigation to it. Navigation is server-driven and the server stays the source of truth while the client is an enhancement, not where your app's state lives.

Cloudflare without the glue

Goribu is Cloudflare-native on purpose. It does not try to make it look like every other runtime. This lets the framework know where it runs, so the platform can become part of the app instead of something you wire together afterwards.

And this enables so many things that improve the quality of life for developers. Supported databases, assets, bindings, migrations and deployment are all part of the same workflow. They are in the code you write. req.d1 is your D1 database. req.cache is the Cache API. req.postgres reaches an external database through Hyperdrive. Static assets and prerendered pages are served straight from Cloudflare's CDN without invoking your Worker. You run one command and migrations, secrets and the app code ship together and you're live.

Who is Goribu for?

It's for developers who want to build and evolve web apps quickly, with great infrastructure defaults already in place. It's for those who tried and want to skip maximum theoretical optimizations from day one, avoid having to edit multiple files for a simple feature change and don't want to be fighting to make it work on the edge.

In the end, it's just JavaScript, React, the capabilities Cloudflare provides and the fastest way from local dev to a deployed app, with all the best practices.

The tradeoff

Goribu is focused and opinionated. So it's not runtime-agnostic as its purpose is to work on Cloudflare perfectly. It's not interested in React Server Components implementations because they add mental overhead and complexity. And it's not trying to cover every possible architecture so it focuses on the happy path.

If none of those are dealbreakers, the rest of these docs show you the whole framework.