Reuse a service across supported runtimes.
For platform teams
Provide. Grant. Consume.
One versioned service across OpenClaw, n8n, and Hermes. Scope and authority are checked at call time.
Request launch access
cgdusek@narthex.one
- Versioned.
- Scoped.
- Governed.
Allow one operation at one version.
Keep Connected Account credentials server-side.
One governed call
Create the issue. Keep the token.
Engineering Ops enables Linear Issue Create once. A Hermes support assistant and an n8n incident flow receive grants to the same operation.
-
01
Requested
Check the call
Narthex checks the exact grant and scope.
-
02
Approval required
Hold the write
Linear is not called while review is pending.
-
03
Executed
Write after review
Narthex calls Linear and records session evidence.
One service. Two runtimes. One policy boundary.
Narthex brokers Connected Account credentials server-side. Linked runtimes do not receive them.
Why Narthex
Not another runtime.
Narthex keeps service contracts, grants, and Connected Account authority outside any one runtime.
Control boundary
Runtimes get operations. Owners keep authority.
Policy is resolved at call time, before side effects.
Exact scope
Grant an operation at a specific service version.
Writes wait
Require approval where policy calls for it.
Credentials stay put
Provider authority stays in the control plane.
Evidence follows
Record who requested the call and how it resolved.
Launch runtimes
Three runtimes. One contract.
Services stay stable while runtimes remain replaceable.
OpenClaw
Provide · discover · invoke
n8n
Provide · invoke · orchestrate
Hermes
Provide · search · invoke
Private launch
Start with one operation.
Tell us what should run, where it should run, and which writes should wait for approval.