GoForjUnreleased

For gophers and agents

The composable
stack for
building with Go

Build and ship Go apps. equips your coding agents with project guidance, skills, and local context.

Get started Explore libraries
go install github.com/goforj/goforj/cmd/forj@latest

Code you own Local-first drivers One app binary

The code

Build more.
Wire less

Serve photos through a small controller and your Go service.

Create the controller

forj make:controller photos
Write a controller
internal/photos/controller.go
go
// Show delegates lookup to the injected service.
func (c *Controller) Show(ctx web.Context) error {
	photo, err := c.service.Find(ctx.Context(), ctx.Param("id"))
	if err != nil {
		return err
	}
	return ctx.JSON(http.StatusOK, photo)
}

Local → production

Swap drivers. Keep your Go

Choose local backends for development, then configure the drivers your deployment needs.

Configuration selects a compiled-in driver at startup. How drivers work →

.env
# Default local drivers
STORAGE_PHOTOS_DRIVER=local
DB_DRIVER=sqlite
CACHE_DRIVER=memory
QUEUE_DRIVER=workerpool
EVENTS_DRIVER=inproc
MAIL_DRIVER=log

Starter kits

Your next product.
Already taking shape

Start with sign-in, account settings, and a dashboard. Choose Vue, React, or Go-rendered HTML with templ + htmx. Make the frontend your own.

Explore starter kits →
Vue starter kit dashboard with navigation and application components
Vue starter kit profile settings with name and email fields
VueVue 3 + shadcn-vueReactReact + shadcn/uitempl + htmxHTML rendered in Go

Your development loop

One command.
Everything running.

forj dev builds your App, runs migrations, and starts its runtimes. Keep editing. It rebuilds as your code changes.

01Choose your stackforj new
02Start buildingforj dev
Get started →Make commands →
Atlas Project guidance and tools for your coding agent
forj dev
┏ Preparing App
┃ + Build
┃ + Migrations · 5
┗ + Prepared
1 App 2 Lighthouse 3 Swagger
┏ App startup · Build App · Run App
┃ 03:18:58.651 Jobs         Queue worker started → default · 30 workers
┃ 03:18:58.651 Scheduler    Scheduler started
┃ 03:18:58.652 HTTP         HTTP server started → :3000 · 27 routes
┗ + Ready · App :3000 · 3 resources · 618ms
● Lighthouse ● API ○ Query Debug 0/ Find x Command ? Help

Lighthouse

Your app,
in plain sight

Browse requests, jobs, schedules, logs, and connected resources. Open an inspect record to see what happened during an execution.

Explore Lighthouse →
Lighthouse request inspect showing a successful HTTP request with seven timeline events, including cache calls, a SQLite query, and the HTTP response

Run it your way

One CLI.
Every app

Start together. Scale independently.

Run HTTP, workers, schedules, and your own custom runtimes together, or give each its own process.

Add an app with forj make:app admin. Share your Go code, with separate wiring and a binary for each app.

Runtime guide →Multi-app Projects →
app ONE PROCESSforj app
ONE PROCESS
PROCESSHTTPforj api
PROCESSWorkersforj worker
PROCESSSchedulesforj scheduler
PROCESSYour runtimeWired by youYour command
Same Go service code
Run built-in and custom runtimes together in one process.
Your server belongs here, too.Wire in a game server, FTP server, or another long-running Go service.
ONE GO PROJECTShared code.
Independent Apps.
internal/Your shared Go packages
appOwn wiring. Own binary.
RUN SOURCEforj app
forj build./bin/app
adminOwn wiring. Own binary.
RUN SOURCEforj admin app
forj admin build./bin/admin
Use forj to run current source. Build once, then deploy the binary without the CLI.

The foundation

The building blocks.
Already connected

Choose what your app needs. GoForj connects the pieces through shared configuration and explicit wiring.

HTTP services

Thin controllers, route groups, and middleware over the web abstraction. Health, readiness, and an OpenAPI reference included.

Commands

First-class CLI entry points with injected dependencies, not shell scripts around your binary.

Queues and jobs

Named, durable background work with typed payloads, retries, timeouts, and worker processes.

Events

Typed facts with local-first fan-out. In-process today, NATS or Kafka when you need it.

Scheduler

Declarative recurring work with stable names, overlap control, and operator visibility.

Database

Named database connections, migrations for each selected driver, and a built-in database shell.

Cache

Named accessors with explicit TTLs, locks, counters, and rate limits behind one contract.

Storage

Named disks for files and blobs. Local in development, object storage in production.

Mail

Fluent message composition with pluggable delivery: SMTP, Resend, Postmark, SES, and more.

Auth

Server-authoritative sessions, HttpOnly cookies, refresh rotation, reset and verification flows.

Metrics and inspects

Prometheus-compatible metrics with bounded labels, plus execution records for every runtime.

Lighthouse

A first-party operator view over routes, inspects, schedules, queues, cache, and storage.

Tested against real backends

First-party libraries are exercised against real services, testcontainers, and emulators.

3,400+test functions in first-party libraries
950+integration test runs against real backends
48drivers across six infrastructure libraries
18libraries you can use independently
Explore the benchmarks →How these numbers are counted →

Your next application

From an idea.
To your first feature

Choose your stack, run your app, and start building what matters to you.

$ go install github.com/goforj/goforj/cmd/forj@latest
$ forj new

Unreleased documentation@latest installs the latest tagged release.

Create your app →Explore on GitHub ↗