Skip to content
How the IMS Go API Starter is put togetherOne Go binary runs the HTTP API, the developer dashboard, the scheduler and the queue workers. Apps call the API, which checks authentication, tenant and permission before reading PostgreSQL. The scheduler enqueues jobs in PostgreSQL, the workers run them and write files to local or S3 storage, and the dashboard records every request and job.Web & mobile appsYou, in a browserone Go binary · imsims serveauth → tenant → permission/dev dashboardrequests · logs · jobs · SQLims schedulecron · no overlapsims queueRiver jobs · retriessame code · same config · one deployPostgreSQLdata · queue · cache · sessionsStoragelocal · S3 · R2

IMS Go API Starter

Laravel's developer experience, Go's performance. A multi-tenant API that ships as one CGO-free binary — it serves the API, runs migrations, queue workers and the scheduler, and embeds a Telescope-style developer dashboard.
from zero to a running API
$ cp .env.example .env && make migrate seedgoose: 24 migrations applied · River schema v8seeded 70 permissions, tenant "Default", admin + developer accounts$ go run ./cmd/app gen module --name=product --fields="name:string,price:decimal"wrote migrations/00025_create_products.sqlwrote internal/modules/product/{model,repository,service,request,handler,routes}.goModule "product" generated.$ make devdashboard  → http://localhost:8080/devAPI docs   → http://localhost:8080/docs

Why this starter

Reads like Laravel

Thin handlers (h.Bind, h.Data), permissions on routes (r.With(h.can("product.create"))), services, repositories and one config file per section. ims gen module scaffolds the stack.

Multi-tenant, safe by default

Tenant and branch isolation in SQL that fails closed, RBAC, impersonation, per-tenant plan limits, and a test that fails any route without a permission.

Everything an API needs

Auth with OTP and recovery · billing with plan limits · settings · feature flags with rollout · activity log · notifications · files on local/S3/R2/MinIO · import/export · backups · queue · scheduler · RFC 9457 errors · OpenAPI.

A dashboard you'll actually use

Requests, logs, exceptions, queue, one-click commands, an inspector for health, routes, roles and config, tenants, settings, flags, files, sessions and an audit log — Ctrl+K to anything.

Fast feedback

Type-safe SQL (sqlc), integration tests in a few lines (testkit), hot reload, and AI-agent skills that know the codebase.

One binary in production

No containers needed: systemd runs the API, the worker and the scheduler from the same binary. Prefer Docker? One image and a compose.yaml run the same stack.

Where to go next