What this enables for corporate and financial services clients
For IT and operations leadership evaluating Lunnoa, this release changes the shape of what "using Lunnoa" can mean. The platform stops being something a team logs into and starts being something a client's existing systems can call directly.
- Every action in Lunnoa requires an interactive session tied to a human user.
- Embedding Lunnoa inside an internal portal, a core banking system, or a partner product means a custom integration project, or scripting around the web UI.
- Machine traffic is throttled the same way as any other traffic from the same network path.
- SuperAdmins mint scoped `lna_...` keys tied to a normal RBAC role and a dedicated service account user.
- A client's own systems call the documented Public API v1 surface directly, with the same permission and licensing checks a human user would face.
- Each key's traffic is throttled independently, so one integration cannot starve another.
Why this matters by function
IT / Security leadership: a governed way to say yes to integration requests
Because every key is a scoped, revocable, RBAC bound service account rather than a shared admin credential, a CISO or IT Director can approve system to system access without approving broad platform access. Revoking a key immediately returns 401 on further calls, and secrets are never stored in plain text.
Operations leadership: automation embedded in the systems people already use
A COO or Head of Ops no longer needs every team member trained on the Lunnoa UI to benefit from it. Existing internal tools, whether a core banking platform, a document management system, or an internal ticketing portal, can trigger and consume Lunnoa workflows directly, which lowers the change management cost of a rollout.
Product and OEM partners: Lunnoa as an embedded engine, not a standalone product
Because the Public API v1 surface is documented, versioned, and access controlled per workspace, a partner, for example a core banking or case management vendor, can white-label Lunnoa's automation capability inside their own product rather than sending their users to a separate application.
Regulated financial institutions: a compliance story that holds together
Self-hosted deployment plus scoped, auditable machine credentials plus a curated public contract is a combination that tends to satisfy internal architecture and security review at banks and asset managers, where an undocumented or over-privileged integration path is often the sticking point in a proof of concept.