Glide OSS

Glide OSS is the open-source orchestration shell behind glide.co — a MIT-licensed full-stack codebase covering the web app, mobile app, MCP gateway, agent skills library, and trust console. Self-hosters bring their own vendor relationships (Privy, Bridge, Chainalysis, Coinbase x402, etc.); the code orchestrates them. This is not a fully self-hostable bank stack. It is a self-hostable orchestration shell with explicit vendor dependencies. The honest framing matters because calling OSS a “money OS” without the vendor-dependency layer creates trust debt.

​

What you can do with Glide OSS

​

Architecture at a glance

​

License + governance

• MIT everywhere. Web, mobile, MCP, every connector, every skill, the CLI. No copyleft anywhere in-tree.
• DCO sign-off on every commit (one-line Signed-off-by trailer, git commit --signoff).
• BDFL at launch. Single maintainer. Governance formalizes when community volume requires it.
• CODEOWNERS-protected changes for _base/ interfaces, trust tier promotions, and money-safety architecture.

See License compatibility for the dependency-license matrix.

​

Trust tiers (quality, not licensing)

Trust is about code-review discipline, not commercial gating. Every package ships under MIT regardless of tier. See Trust tier.

​

Money-safety F-rules

Every money-touching tool path observes seven IRON-RULE contracts: (F6 reserved.) Detail at Money-safety contracts.

​

Where to start

• Self-hoster → Quickstart → Self-hosting
• Connector author → Connector catalog → Adding a connector
• Skill author → Skill catalog → Authoring a skill
• Agent integrator → Headless MCP → OAuth flow → Tool reference
• Standards reader → Standards
• Security reviewer → Threat model → License compatibility

​

Source code

github.com/darshanbathija/axtior-neobank — the monorepo. Issues, PRs, discussions all there. CONTRIBUTING.md has the full partner-PR flow.