Soroban gave Stellar a real smart contract platform. Quantara exists to give Soroban developers the tooling around it that most modern platforms take for granted: a place to manage projects, a real deployment workflow, and a way to verify what's actually on-chain — instead of ad-hoc scripts and manual bookkeeping.

Quantara brings patterns from modern cloud developer tooling (think: a lightweight Heroku/Vercel-style dashboard) to Soroban smart contract development.

Developer
    |
Quantara Web    →  dashboard: create projects, deploy, inspect what's on-chain
    |
Quantara Core   →  REST API: project management, deployment workflow, contract registry
    |
Soroban Contract → on-chain DeploymentRegistry, verifying what was actually deployed

Every repo here is an early, honest foundation — not a finished product. We'd rather ship something small that's real end-to-end (a working API, a working dashboard, a real Soroban contract, real tests, real CI) than something that looks bigger on paper but doesn't actually run. Every corner we've deliberately cut — no authentication yet, the deploy workflow is simulated rather than hitting a live network, no CLI yet — is documented in the relevant repo's README rather than hidden. If something looks unfinished, it's called out on purpose, not by accident.

The dashboard UI is live at quantara-web.vercel.app for a look at the interface, but it isn't wired to a running quantara-core backend, so pages that fetch data won't work there. For the real create → deploy → verify flow, run both locally:

# 1. backend + database
git clone https://github.com/quantarahq/quantara-core.git
cd quantara-core/infra && docker compose up -d

# 2. dashboard, in another terminal
git clone https://github.com/quantarahq/quantara-web.git
cd quantara-web && npm install && npm run dev

Then open http://localhost:3000, create a project, hit "Deploy Contract", and watch it show up in the deployment history and contract registry tables — every step is a real API call, not sample data.

Every repo enforces its own quality bar in CI, not just locally: Checkstyle + Spotless for Java, Clippy + Rustfmt for the contract, ESLint + Prettier + Vitest for the frontend.

We'd genuinely rather have a few real contributors than a lot of drive-by PRs, so:

• Start with the good-first-issue and help-wanted labels on quantara-core or quantara-web.
• Every repo has its own CONTRIBUTING.md with concrete setup steps and the exact commands CI runs, so there are no surprises between your machine and CI.
• quantara-toolkit isn't ready for implementation PRs yet — see its README for why, and open a design-discussion issue there instead if you have thoughts on the future CLI or runtime.

Labels shared across the org: good-first-issue, help-wanted, backend, frontend, smart-contract, documentation, infra, MVP, future.

Everything here is MIT licensed.