ZG
Luas Modular Go API scaffold for real product work
Running STAGING
Base URL http://localhost:8025
Pure Go API scaffold

Start shipping backend work without rebuilding auth, API keys, or CLI plumbing.

This homepage is here to answer the first three developer questions fast: did the service boot correctly, what ships by default, and what should I do next.

Check Health Read GitHub Docs
Default starters User auth, API keys, and audit logging are already wired.
CLI seam Generation, migration, and AI commands share one manifest surface.
Extension path Add modules behind starter manifests instead of editing five boot files.

Get productive in three moves

A starter home page should prioritize the next useful actions: verify the service, inspect the active interface, and start changing code.

Step 01

Verify the service

Confirm that the service is running, configuration loaded correctly, and database or middleware setup did not block startup.

GET http://localhost:8025/v1/health
Step 02

Explore the default API

The default scaffold includes authentication, API key management, and global audit logging. Inspect the registered routes before adding another starter.

go run ./cmd/luas route:list
Step 03

Generate the next module

Start with a complete module scaffold instead of assembling unrelated files. Use single-file generators only to extend an existing module.

go run ./cmd/luas make:module Invoice

What ships in the default scaffold

These are the product-neutral surfaces that are active now, without retired deployment-platform or control-plane behavior.

Starter

User auth

Registration, login, revocable sessions, current-user profile, and password flows provide a practical baseline for most backend projects.

Starter

API key access

Key creation, listing, revocation, and middleware groups support automation and service-to-service access from the default scaffold.

Starter

Audit logging

Write requests are audited globally and users can query their own history, making traceability part of the baseline instead of a downstream patch.

Know the shape of the app

This architecture map helps product managers, technical leads, and new developers build an accurate mental model instead of scanning feature badges.

Core

Runtime and infra

Bootstrap, routing, responses, migrations, testing, and shared packages form the foundation used by every Luas application.

Starter

Business-ready defaults

user, apikey, and audit are assembled by default. Their starter manifests contribute modules, migrations, and seeders.

Capability

Reusable technical seams

Technical capabilities such as AI stay in the capability layer so external integrations do not become broad business modules.

Optional starter

Keep expansion explicit

Enhancements such as RBAC remain available without entering the default scaffold path, keeping both the baseline and optional extensions honest.

Default endpoints

Ready-to-call routes

Verify these interfaces first after startup to confirm that the default starter behavior is healthy.

  • POST/v1/register
  • POST/v1/login
  • GET/v1/users/profile
  • GET/v1/api-keys
  • GET/v1/audit-logs
  • GET/v1/health
Direct links

Fast paths for the next click

Only decision-relevant destinations belong here. The home page should expose likely next actions, not every available link.