Before you build

Roadmap — what's landing next

No dates and no now/next/later tiers — just what's being built, in full. The homepage shows the four items most people ask about first; everything below is the complete list. Every item here arrives under the same definition-first model the rest of Aaly runs on, so nothing on your side gets rewritten when it lands. See Limits for what's a real gap today, with a workaround for each.

Shipped since August

These were on this page as planned work and are now live. Details in the docs; gaps that remain are on Limits.

File storage — presigned uploads, a built-in files entity, and files attachable from your own entities.
Custom functions — your own server-side Python on an entity's request lifecycle, on any method, before or after, sync or async. Webhooks and third-party integrations are just functions.
Custom endpoints — non-CRUD routes backed by functions, with the platform's auth and tenant scoping still applied.
Refresh tokens — a 1-hour access token with a rotating refresh token, replacing the flat 7-day JWT.
Request and function logs — per-request and per-execution logs, with a request id that correlates the two.

See the changelog for the complete release-by-release history, including everything shipped before this list was last cut down.

Multiple environments

Development, staging, and production from one definition — promoted, not re-implemented.

Roles and permissions

Role- and field-level access inside a tenant, enforced by the platform the way tenant isolation already is.

Scheduled functions

Your functions on a schedule rather than only on a request — recurring work without a server to keep awake.

Per-project MCP servers

Every project exposes its own tools, so an agent can operate that product, not just the platform.

Vector search

Semantic search over your entities, without standing up a second database to hold copies.

Structured RAG

Retrieval grounded in your data model and its relationships, not in a pile of loose documents.

Reporting

Aggregations and reads across entities, defined the same way everything else is.

Auditing

A record of who changed what, kept by the platform rather than remembered by your code.

Everything below the "Shipped since August" block is still planned, not built. See the homepage and docs for what's live today, and Limits for the gaps that remain.