Case Study · 008Compliance-driven build · deliveredEnterprise partner · Bunge

Compliance-ready traceability — built for the EU deadline.

Justoken (formerly Agrotoken) faced a regulatory deadline that doesn't move. Two production portals — public traceability and a Bunge enterprise admin — built on a complex blockchain stack, audit-ready the day the law went live.

Client: Justoken (formerly Agrotoken)
Sector: Agritech · Commodities · Blockchain · RWA
Engagement: Compliance-driven build · multi-quarter
Enterprise partner: Bunge
Portals shipped: 2 — public + enterprise
Regulation: EU sustainability / traceability lawTBD

2Production portals shipped

On timeEU compliance deadline

BungeNamed enterprise partner

TBDTraceability documents servedTBD

01A regulatory deadline that doesn't move.

When the law goes live, the portal has to be there — not on a Jira board.

Founded: Originally as Agrotoken
Sector: Agritech · RWA · Blockchain
Enterprise partner: Bunge (Fortune 500 agribusiness)
Trigger: EU sustainability / traceability deadlineTBD
Engagement model: Compliance-driven managed build

Justoken (formerly Agrotoken) pioneers real-world asset tokenization for agriculture — bringing blockchain-backed infrastructure to commodity trading. It is the first global platform of its kind to turn grain, oilseed, and other agricultural assets into auditable, on-chain instruments that traders, banks, and producers can rely on.

When the EU's sustainability and traceability law set a hard regulatory deadline, Justoken faced a problem with no slip in it: every commodity transaction inside the EU would need accessible, auditable traceability documentation, or the trade simply wouldn't clear.

Meeting the deadline required two production-grade portals at the same time — a public-facing traceability portal for external stakeholders, and a secure enterprise portal for Fortune 500 agribusiness Bunge — all on a complex blockchain stack, with an internal Justoken engineering team being stood up in parallel.

02The Challenge

A deadline that doesn't move. An audit that doesn't forgive.

Most builds bend on scope when timelines get tight. Compliance builds can't. The EU regulator wasn't going to grant an extension because the team was new or the chain was complex. Either the portals were live and audit-able when the law went live, or Justoken's commodity flow stopped clearing.

A hard EU compliance deadline.

The EU's sustainability and traceability law set a fixed go-live date. Miss it and commodity transactions inside the EU simply wouldn't clear. There was no equivalent of 'shipped late but it's fine' — there was 'shipped' or 'not trading'.

Regulatory

Two portals. One deadline.

One deadline, two production portals: a public traceability surface for external stakeholders, and a secure internal portal for Bunge with enterprise access control, order management, and audited document flows. Both had to land in the same window.

Scope

A new team standing up in parallel.

Justoken's internal engineering team was being formed in parallel with the build. The architecture, conventions, and tooling we set would either become the foundation that team inherited cleanly — or technical debt before they wrote a line.

Team formation

Blockchain complexity, end-to-end.

Blockchain infrastructure, Ethereum integration, audit-able document chains, and enterprise security all in the same codebase. Each choice carried a multiplier of technical risk that couldn't be paid down after the regulatory go-live.

Technical risk

Streaver got us audit-ready before the deadline we couldn't afford to miss.

JustokenTBDEngineering Leadership · Justoken

03Selection

Why Justoken picked us for the deadline.

On a compliance build, the selection question isn't “who's cheapest” or “who's fastest” — it's “who do we trust with a regulatory go-live we can't move?” Three reasons that decision landed with us.

Compliance-first architecture, not retrofitted.

Justoken couldn't bolt compliance on after the build. The EU's traceability requirements had to be baked into the data model, the chain design, and the document export flow from day one. Streaver came in with a compliance-first architecture mindset and worked backwards from the regulator's requirements, not the feature backlog.

Deadline delivery, production-grade fast.

A regulatory deadline is the cleanest measure of a partner's discipline. It rewards teams that can hold scope, ship production-grade quality fast, and refuse to negotiate timelines that legally can't be negotiated. Streaver had delivered against fixed regulatory deadlines before — and could speak credibly to the trade-offs that get a portal across the line on day one.

Team foundation, not just a delivery.

Justoken's own engineering team was being assembled in parallel. The technology decisions we made — monorepo, NestJS, conventions, CI — were the team's first week of orientation. We set them as a foundation that would survive the team's growth, not as scaffolding the next hire would tear out.

04The Chain

From commodity to audit-ready, in five steps.

The chain below is the architecture, not a metaphor. Every step is a real handoff with a real signature attached — what makes a certificate exportable on the last node is what was captured at the first. Audit-grade evidence as a by-product of how the system already works.

Five steps · zero gaps

STEP 01CommodityPhysical asset enters the chain
STEP 02TokenizedOn-chain record minted
STEP 03Traceability docAccessible via the portal
STEP 04CertificateXLS / CSV export, signed
STEP 05Audit-readyEU compliant · evidence captured

Each step is logged, signed, and exportable. Compliance isn't an audit-time scramble — it's the natural output of the chain.

+ Image placeholder

Traceability workflow diagram · commodity → tokenized → audit. Suggested: a single illustration that shows the chain of custody as one flow with the two portals (public + Bunge) hanging off the same compliant core.

05Decisions

Three calls that bought us the deadline.

Monorepo first — for the team that didn't exist yet.

With a new team coming online and two portals to ship from the same primitives, a fragmented multi-repo set-up would have cost us weeks in tooling drift alone. We standardized on a single monorepo so the same engineer could move from the public portal to the Bunge portal without re-learning a build, and so new hires onboarded into one source of truth.

ResultBoth portals shared types, schemas, and chain-integration utilities from week one. Conventions held as the Justoken-side team grew.

NestJS as the foundation a new team can read.

We chose NestJS as the backbone for both portals — not because it was the fastest framework on a benchmark, but because its opinionated module system, dependency injection, and convention-over-configuration ethos are exactly what a forming team needs to inherit. Patterns that survive the founding engineer leaving are the ones that pay off across a multi-quarter compliance build.

PrincipleThe right foundation is one a team you haven't hired yet can read on their first day and contribute to on their second.

Dual-portal, single compliant foundation.

It would have been faster, in the short term, to build the public traceability portal and the Bunge enterprise portal as two unrelated apps. We resisted that. Both portals share the same chain-of-custody data, the same certificate generation, and the same audit guarantees — they just expose different slices of it. One compliant core. Two consumer surfaces.

06Honest

What we can't yet say cleanly on this page.

We'd rather flag the gaps than dress them up. Each item below is something we have a working answer to internally but don't yet have a Justoken-signed-off public number for.

Timing · TBD

Met on deadline — comfortably, or at the wire?

The brief on this engagement says 'EU deadline · met on time.' What it doesn't say is whether we crossed the line with weeks to spare or whether it was a tight final sprint. Both happen on regulatory builds — and on the next one of these we'll publish the answer, because the difference matters to a buyer judging us.

Regulation · TBD

We haven't named the specific regulation publicly yet.

The source materials reference 'the EU sustainability and traceability law' without naming the specific regulation. It's most likely EUDR (EU Deforestation Regulation), but we'd rather mark it TBD here than confidently name the wrong one and undermine the credibility of everything else on the page.

Volume · TBD

Throughput numbers are not yet board-quotable.

How many traceability documents flow through the public portal in a typical week? How many contracts have been processed through the Bunge side? We have working answers internally; we don't yet have publication-ready numbers signed off by Justoken and Bunge. When we do, those replace the TBD badges on this page.

07Outcomes

What shipped — and what it changed.

Each outcome below pairs the after state with the baseline it's measured against. The leading outcome — “EU deadline met” — is the one Justoken hired us for, and the one that paid for everything else.

Open exposure on a fixed regulatory dateOn time — both portals in production

EU compliance deadline met.

The EU compliance go-live landed with both the public traceability portal and the Bunge enterprise portal operating against real chain-of-custody data — not a staging environment, not a demo, not a beta flag.

Manual contract handling per transactionAutomated, API-driven uploads

Manual contract uploads automated.

Contract uploads to the Bunge portal moved from a manual back-office process to API-driven automation, removing a category of error the enterprise security team would otherwise have flagged on audit.

Hand-assembled compliance packetsProgrammatic, signed XLS / CSV exports

Certificate generation automated.

Traceability and sustainability certificates are now generated on demand and exported in the formats the EU regime accepts. Compliance evidence is an export, not a workstream.

Team being formed, no shared foundationConventions, tooling, CI — inheritable on day one

Scalable foundation for the new team.

The monorepo, NestJS conventions, and CI pipeline became the onboarding for Justoken's new internal engineers. The foundation outlasts any one contributor and scales with the team rather than against it.

No internal portal at allLive — enterprise security, audit-able

Bunge enterprise integration shipped.

Bunge — a Fortune 500 agribusiness — now operates orders, users, and documentation through the secure internal portal we shipped, under invitation-based access and granular permissioning.

Compliance as a scramble at audit timeCaptured at the source, exportable

Audit-ready evidence chain.

Every step on the chain — commodity, tokenization, traceability doc, certificate, audit evidence — is logged and signed at the point it happens. Compliance becomes the natural output of the chain, not a separate workstream chasing receipts.

08The Team

Four Streavers. Two stakeholder loops. One deadline.

A compact senior team paired with Justoken's forming internal team — and Bunge's enterprise stakeholders on the other end of the second portal. Continuity across every gate was the only way the regulatory date stayed honest.

Engagement LeadTBD

Engineering Lead

Owns the engagement, scope-management against the regulatory deadline, and the joint cadence with Justoken and Bunge stakeholders.

Backend EngineerTBD

Senior NestJS Backend

Designed the NestJS module structure, the chain-integration utilities, and the audit-export layer that both portals share.

Frontend EngineerTBD

Senior Frontend (React)

Built the public traceability portal and the Bunge admin surface against a single shared design system — different surfaces, one component library.

Blockchain EngineerTBD

Senior Blockchain (Ethereum)

Owned the Ethereum integration, on-chain record design, and the signing and verification flow that makes the certificate exports audit-grade.

How the engagement is structured

Cadence

Weekly compliance-progress review with Justoken leadership, plus a separate biweekly review with the Bunge stakeholders on the enterprise portal. Daily Slack standups across the joint team.

Communication

Two stakeholder loops in parallel — Justoken on product and chain design, Bunge on enterprise security, access control, and admin requirements. Both fed the same backlog, on the same deadline.

Pricing

Milestone-priced against compliance gates, not headcount. Each gate corresponded to a regulator-checkable deliverable: chain design, public portal v1, Bunge portal launch, audit-prep package, deadline cleared.

IP & security

Justoken holds every credential, every repository, every chain key. Streaver operated as a managed build partner against the regulatory deadline — never as a custodian of access the client couldn't replace.

From law-on-paper to law-in-production

WEEK 00Regulatory research completeMapped the EU regulatory requirements to concrete data, document, and export obligations. Defined what a compliant chain-of-custody actually had to prove.

WEEK 06Foundation in placeMonorepo, NestJS conventions, shared TypeScript types, CI/CD, and the chain-integration utilities. The Justoken team's onboarding starts here.

WEEK 12Public portal · v1Public traceability portal v1 — commodity, tokenized record, document access, and signed XLS/CSV export — operating against real on-chain data.

WEEK 18Bunge portal launchedBunge enterprise portal goes live: invitation-based user management, granular permissions, API-driven contract uploads, and audited document flows.

WEEK 22Compliance audit prepEnd-to-end audit-prep: evidence chain, certificate exports, access logs, and a signed snapshot of the compliance state. Independent dry-run against the regulator's checklist.

WEEK 26EU deadline clearedEU sustainability and traceability deadline reached with both portals in production and audit-able. Justoken's commodity flow keeps clearing.

09Stack

Disciplined choices for a foundation that outlives the deadline.

Every technology decision on this build had to be readable by a team that didn't exist yet, and auditable by a regulator who'd never seen the code. We optimized for both constraints, not for the framework leaderboard.

Languages & Backend

TypeScriptstrict, end to end
NestJSshared backbone for both portals
Reactfrontend across public + Bunge surfaces

Blockchain

Ethereumon-chain record of every tokenized commodity
On-chain signaturessigning and verification at the certificate boundary
Custom chain libschain-integration utilities shared across portals

Infrastructure

AWSprimary cloud
Monorepo toolingsingle source of truth across portals & libs
CI/CDtied to compliance gates, not just merges

10What's Next

The deadline was the start, not the finish.

The EU go-live unlocked the rest of the roadmap. The same compliant core now extends into deeper traceability, new regulatory regions, and a public API surface for the regulated parties downstream of Justoken.

Expand traceability coverage.

Deeper traceability flows — multi-step custody transfers, lot-level provenance, and richer sustainability evidence — building on the same compliant core, not a parallel stack.

New regulatory regions.

Apply the same compliance-first architecture to other regulatory regimes — UK, US, LATAM — so Justoken can take the same operating model into new markets without rewriting the chain.

API ecosystem for banks, insurers, traders.

Open an API ecosystem for banks, insurers, and traders who consume Justoken's traceability evidence as a first-class input. The chain becomes infrastructure other regulated parties build on.

Regulatory deadline you can't move?

Compliance-as-architecture is what we do.

Streaver delivers regulated, audit-ready builds against fixed regulatory deadlines — and sets the engineering foundation that outlives the deadline by years. If you're staring down a date the regulator picked for you, let's talk early.

Book a discovery call See more case studies

11Continue reading

Featured

Live

AIBuildRegulatedPublic Affairs · Switzerland

DELOS AG

First paying enterprise customers in sixteen weeks

91% precision · 4-agent systemRead the case study

Featured

Live

BuildScaleAISports tech · Marketplace · US

Supreme Golf

Building a $1M product for $125K with a non-technical CEO at the keyboard

8× lower cost · 3–5 deploys/dayRead the case study

Back to all case studies