Language overview
Atlantus apps are multi-file .atl modules under app/. The CLI compiles
them and the runtime serves HTTP routes.
What you write
- Functions and route handlers in
.atl - JSON-friendly values: numbers, strings, bools, arrays, maps
- Null checks with
none - Modules with
import
Types (practical)
| Type | Notes |
|---|---|
Int, Float, Bool, String | Scalars |
| Arrays / lists | Ordered values |
Maps / { "k": v } | JSON objects |
| Request / Response | Inferred at the HTTP boundary |
Day to day, rely on atlantus check for type and arity errors.
Modules
module users
import services.users as Users
Paths under app/ map to import paths. Prefer matching the scaffold’s style.
Built-ins
HTTP, request, DB, auth, and jobs helpers are built into the runtime.
See Built-in API.
Dev vs production
| Command | Typical use |
|---|---|
atlantus dev | Fast compile, great DX, optional --watch |
atlantus start | Production-shaped process |
You write the same .atl either way.
How it runs (optional)
Internally the toolchain compiles to bytecode (and may AOT hot paths). You do
not configure compiler crates as an app author — install atlantus and focus on
.atl.
Next: HTTP & JSON.