Documentation previewThese docs are actively being built. Some pages may change as the framework and examples are finalized.
GoForjv0.9

The composable stack for building with Go

Build Go applications with one cohesive runtime, explicit dependency wiring, local-first drivers, and production-ready primitives for HTTP, queues, events, storage, cache, scheduling, and observability.

Driver swappableChange infrastructure without rewriting application code.
Explicit runtimeGenerated wiring and lifecycle behavior stay inspectable.
Local firstStart locally, then move to production topology when needed.
Explore LibrariesDesign Philosophy
rear-supportgroundRUNTIMERUNTIMECORE GOFORJ CORE goforjgoforjgoforjgoforjgoforjplatform-shelfrear-shelfBackend libraries and infrastructureBACKENDCore librariesCORE LIBRARIESlower-shelfFrontend choicesFRONTENDCollectionsStringsVueEnvQueue libraryQUEUEHTTPXCryptReactRedis QueueRabbitMQ QueueAmazon SQS QueueEvents libraryEVENTSNATS QueuePostgres QueueAI agent providersAI AGENTSMariaDB Queueassembly-input-leftSQLite Queueassembly-resultNATS Eventsassembly-input-rightNATS JetStream EventsOpenAIKafka EventsStorage librarySTORAGERedis EventsAmazon SNS EventsClaudeGoogle Pub/Sub EventsLocal StorageGeminiMemory StorageFTP StorageDatabase backendsDATABASERedis StorageSFTP StorageGoogle Cloud StorageAmazon S3 StorageDropbox StorageMariaDBRclone StoragePostgresCache libraryCACHESQLiteFile CacheMemory CacheRedis CacheMemcached CacheNATS CachePostgres CacheSQLite CacheMariaDB CacheDynamoDB Cache

One application experience

Explicit configuration, no hidden globals, and clear escape hatches. You always know what a tool is doing.

Ergonomics without magic

Fluent APIs that reduce noise while preserving Go’s clarity, types, and explicit control.

Production-first behavior

Designed for real workloads: predictable errors, deterministic execution, and no surprising defaults.

Local-first infrastructure

Start with local drivers, then swap infrastructure backends through configuration and providers without rewriting business logic.

Libraries you can compose

Each first-party library stands on its own and also fits underneath generated GoForj App abstractions.

Tools you can inspect

Runtime behavior, metrics, inspections, and generated code are designed to be auditable.

Two Ways To Use GoForj ​

GoForj supports two valid adoption paths.

Use the framework docs when you want a cohesive GoForj App with runtime orchestration, generated components, explicit dependency injection, local-first drivers, and production-oriented operations.

Use the library docs when you want standalone first-party Go packages that can be adopted independently in existing Go services, CLIs, and workers.

Start Here ​

  • Getting Started introduces the generated App path.
  • Runnable Scenarios are the main guided path after Quickstart: route, cache, storage, events, jobs, schedules, and observability.
  • Core Concepts explains the framework model behind Apps, runtimes, providers, drivers, and generated components.
  • Libraries collects standalone first-party Go packages.
  • Operations explains how GoForj applications run, observe, and shut down.