Hara Exchange
Hara Exchange lets government agencies, businesses, and citizens share data peer-to-peer under the data subject's cryptographic consent — never through a central hub. Built on UU PDP, GDPR, NIST PQC, and W3C DID standards.
HaraLens, HaraSchema & HaraLink now run trained models (MLflow-registered, served by hx-infer): PII detected from value patterns even in mis-named columns, entity matches scored by a learned model. Every decision feeds a label back; weekly auto-retraining.
Real BBS+ (BLS12-381) credentials: the cross-border EUDR proof reveals only “deforestation-free”, while geolocations and farmer identities stay sovereign. UU PDP data-minimisation, cryptographically enforced.
Vault out of dev-mode (raft + audit + auto-unseal + daily snapshots), signing keys in Vault, off-host backups, Prometheus alerting, and a tested restore drill.
Members, services and grants registered live on the Hara Registry — BRI Agroniaga onboarded as a member, provider and authorised consumer.
Every envelope carries Ed25519 + ML-DSA-65 dual signatures (NIST FIPS 204). Connection is authenticated if either signature verifies — protecting you across the quantum migration.
Personal-data exchanges require a signed consent record on HaraLedger before they can be transmitted. UU PDP §32 enforced in protocol, not policy.
12 UU PDP / GDPR / OJK / charter rules evaluate every exchange before signing. Refused exchanges never hit the wire — and every refusal cites its rule.
Append-only Merkle log + hourly IOTA root anchor. Court-grade ASiC-E export bundle in one HTTP call.
HaraLineage walks the provenance graph and produces a per-system DELETE / ANONYMIZE / NO_ACTION plan automatically. UU PDP §43 closed.
No central hub. Each organisation runs its own HaraGate; data flows directly. The blockchain only holds identity, consent, and access — never payloads.
TypeScript · Python · Go · Java · Kotlin · Rust. All generated from one OpenAPI 3.1 spec. Time-to-first-exchange < 15 minutes.
HaraGuard catches anomalies on metadata only; HaraFraud detects rings via Neo4j graphs; HaraLink assembles Golden Records from multiple sources.
SOAP / HL7 v2 / fixed-width / DB row adapters. Connect Coretax, BPJS legacy systems, hospital LIS, and mainframes without touching their code.
Every product decision must satisfy at least one. If it serves none of these, it is not built.
Click any module for syntax. Each card has a Run live button when a working demo is wired.
HaraBridge normalizes these formats on the wire (SOAP→REST, HL7→FHIR, DB→REST, flat-file→JSON) so a provider can expose legacy data without re-platforming. Providers review and approve access to their data in the Hara Provider console.
| Extension | Format | What happens on upload |
|---|
Column names matching NIK, NPWP, nama, alamat, email, dob, phone are flagged and surfaced in HaraComply rule R-06 (data-minimisation).
CSV / JSON / database-row uploads can be turned into formal OpenAPI 3.1 schemas via HaraSchema (/v1/schema/infer).
HL7 v2 → FHIR R4, SOAP → REST, EDIFACT → JSON, fixed-width → JSON via HaraBridge adapters.
A capability ladder — from a single question to a multi-ministry, privacy-preserving exchange. Every Live rung runs against the real staging stack.
Every demo tells the same simple story: someone asks for data, the platform checks whether that's allowed, fetches only what's permitted, and writes down exactly what happened — so nothing ever moves without consent, a lawful purpose, and a tamper-proof record. Here is the journey, and the one job each Hara Exchange component does in it:
Not every rung uses every step — e.g. an open-data question (rung 1) skips the grant/consent check, while the compliance gate (rung 3) stops at step 3 on purpose. The higher rungs simply chain more of these together (rung 5 runs steps 2–6 four times in parallel; rung 6 adds a privacy-preserving join via HaraLink).
Behind every demo, a single exchange runs through these eight steps. In plain terms: ask securely → check it's allowed → prove it's authentic → deliver → record it forever. Each step is a real Hara Exchange component; the technical name is in brackets.
From clone to your first signed exchange in 15 minutes. Six SDKs — TypeScript · Python · Go · Java · Kotlin · Rust — all generated from one OpenAPI 3.1 spec. The two consoles above are built on the same public API.
curl /api/catalog/v1/services curl /api/provider/v1/published
curl -X POST /api/query/v1/ask -H 'content-type: application/json' \
-d '{"question":"Total oil-palm area by district?",
"consumerDid":"did:hara:org:dev-bappenas"}'
curl -X POST /api/gate/admin/exchange -H 'content-type: application/json' \
-d '{"providerDid":"did:hara:org:dev-hara",
"service":"did:hara:service:hara-farmer-profile-v2",
"subject":"did:hara:person:dev-ahmad-fauzi",
"purpose":"credit_assessment","body":{"nik":"1404125508920001"}}'
from haraxchange import HaraClient
hx = HaraClient("https://exchange.haratrust.io/api/gate")
out = hx.exchange(
provider_did="did:hara:org:dev-hara",
service="did:hara:service:hara-farmer-profile-v2",
subject="did:hara:person:dev-ahmad-fauzi",
purpose="credit_assessment",
body={"nik":"1404125508920001"})
print(out["credit_score"], out["_hx"]["consentId"])
The full HaraGate admin surface — every SDK is generated from it.
The asker's console: ask in natural language, get a cited answer. Built on /api/query.
The owner's console: onboard data, set access, approve requests. Built on /api/provider.