Skip to main content
ARQERA
FeaturesOreOjuIntegrationsDocs
Request Early Access
Open Source

Open where it matters.
Protected where it counts.

Our SDKs, connectors, and client libraries are fully open source. The governance engine that makes AI safe stays proprietary. Clear boundaries. No surprises.

View on GitHubRead the Docs

MIT licensed · Production ready · Community driven

Fully open source

Build with everything you need.

SDKs, connectors, and libraries. Fork them, extend them, ship them. No vendor lock-in on the integration layer.

Python SDK
MIT

Full-featured Python client for the ARQERA API. Type-safe, async-first, battle-tested. Install with pip and go.

TypeScript SDK
MIT

First-class TypeScript support with full type inference. Works with Node.js, Deno, and edge runtimes.

Connectors
Apache 2.0

Pre-built integrations for Slack, GitHub, Jira, Stripe, and more. Fork them. Modify them. Build your own.

Client Libraries
MIT

Lightweight wrappers for Go, Ruby, and Java. Community-maintained with official support.

Proprietary core

The engine stays ours.

The governance engine, routing intelligence, and compliance frameworks are what make ARQERA different. They stay proprietary so we can keep innovating on the hard problems that make AI safe for production.

You get full access through the platform and APIs. The SDKs are your interface. The engine is our responsibility.

Governance Engine

The 5-layer AI governance model. Policy enforcement, trust scoring, evidence chains.

Routing Intelligence

Multi-model routing that picks the right AI for every task. Cost, speed, and capability optimised.

Compliance Frameworks

GDPR, EU AI Act, SOC 2 control mappings and monitoring. Built by compliance engineers.

Evidence & Audit

Immutable evidence chain. Every AI action recorded, attributable, and legally defensible.

Our philosophy

Open core. Done right.

We believe open source and commercial software can coexist without compromise.

Transparent by default

Every SDK method is documented. Every API response is typed. Every connector shows its source. You always know what your code is doing.

Community first

Bug reports get fixes, not workarounds. Feature requests get PRs, not "we'll consider it." Contributors get credit, always.

Clear boundaries

No bait-and-switch. No open-washing. The line between open and proprietary is drawn clearly and will not move. Your integrations are yours.

Contribute

Fork it. Fix it. Ship it.

Every contribution matters. From typo fixes to new connectors. Here's how to get started.

01

Fork the repo

Pick an SDK or connector. Fork it on GitHub. Clone locally.

02

Build your feature

Create a branch, write tests, make your change. Follow the contribution guide.

03

Open a PR

Submit a pull request with a clear description. Sign the CLA. We review within 48 hours.

04

Ship it

Merged PRs are released in the next SDK version. Your name goes in the changelog.

License policy

SDKs are MIT licensed. Connectors and example workflows are Apache 2.0. We check all dependencies for license compatibility before every release. GPL and AGPL dependencies are not accepted due to viral licensing terms.

Growing together

Built in the open.

4
Open repositories
100%
SDK test coverage
MIT
SDK license
arqera-pythonPython SDK
MIT
arqera-jsTypeScript SDK
MIT
arqera-connectorsIntegration connectors
Apache 2.0
arqera-examplesExample workflows
Apache 2.0

Build with us.

Star us on GitHub. Open an issue. Submit a PR. The code is yours.

View on GitHubRead the Docs

Product

  • Ore
  • Oju
  • Integrations

Solutions

  • For Developers
  • For Operations
  • For Startups
  • Compliance

Resources

  • Documentation
  • FAQ
  • Open Source

Company

  • About
  • Security
  • Privacy
  • Terms
  • Cookies
  • Legal
© 2026 ARQERA. All rights reserved.