Our Values

1. Quality

Aurora exists to give teams a better AI gateway than the alternatives. Quality is how we get there.

An AI gateway does not have to be written in Python. Go was chosen because runtime behavior, deployment shape, memory profile, single-binary distribution, and long-term maintainability matter more than developer ergonomics at small scale. The resulting binary is fast, statically linked, and easy to operate in any environment.

The "jar" principle applies: if you fill it with sand first, the larger stones will not fit later. In Aurora, the big stones are:

• The request lifecycle — auth, workflow selection, guardrails, cache, failover, provider call, audit, usage, response.
• The configuration model — three layers (code defaults, config.yaml, environment variables), with no surprise behavior.
• The operational surface — logs, metrics, audit, live console, dashboard.

Features and fixes are the sand. They are added on top of a solid foundation, not at the cost of it.

2. Efficiency

Efficiency applies to the runtime and to how we work.

On the runtime side, the gateway is built to do as little as possible per request. Provider call latency dominates; everything around it has to be cheap. The cache is exact-match and vector-search with a tight TTL. The audit write is buffered and async. The heartbeat is coarse-grained. The dashboard uses the same data the gateway already has. There is no daemon you forgot to start and no service mesh dependency to misconfigure.

On the work side, we use the same AI tooling everyone else does — Claude Code, Codex, CodeRabbit, Copilot. The point is not the tool, the point is the loop: a change ships with a test, a doc update, and a changelog entry, in one PR, every time.

3. Transparency

Aurora is open source and we want to keep it that way. The project needs to be sustainable; sustainability usually means money; money usually means enterprise. None of that has to mean closed source, but it does mean being honest about the trade-offs.

The principle in practice:

• The default license is Apache 2.0.
• The anonymous heartbeat ships opt-in via env var and is documented down to the field level.
• The release process is open: changelogs, signed releases, public roadmap.
• The pricing for Enterprise is published, not negotiated. If a procurement team needs a quote they get one in writing.

How values become decisions

A few examples of trade-offs these values resolve:

Related

• Who We Are — the team and community
• Technical Philosophy — the engineering ideas that shape the code
• Roadmap — what is shipping next
• License — the current license and what could change