Now building

The logistics layer EU supply chain compliance is missing.

koto7 is a headless multi-tenant engine with two arcs: operational logistics orchestration and EU-grade Digital Product Passport compliance — built in one of the world's hardest logistics environments.

Arc A: Logistics operations · Arc B: Digital Product Passport

go
// koto7 — DPPPassportLifecycleWorkflow
// Survives years of ownership transfer,
// certification, and end-of-life

func DPPPassportLifecycleWorkflow(
	ctx workflow.Context,
	passportID string,
) error {
	logger := workflow.GetLogger(ctx)

	for {
		selector := workflow.NewSelector(ctx)

		var signal PassportSignal
		signalChan := workflow.GetSignalChannel(
			ctx, "PassportEvent")

		selector.AddReceive(signalChan,
			func(c workflow.ReceiveChannel, _ bool) {
				c.Receive(ctx, &signal)
			})

		selector.Select(ctx)

		// Update passport state durably
		err := workflow.ExecuteActivity(ctx,
			UpdatePassportState,
			passportID, signal,
		).Get(ctx, nil)
		if err != nil {
			logger.Error("state update failed",
				"error", err)
		}

		// Mint to public chain on certification
		if signal.Type == "CertificationReceived" {
			workflow.ExecuteActivity(ctx,
				MintStateHash, passportID)
		}

		// continueAsNew — stay within
// Temporal history limits
		info := workflow.GetInfo(ctx)
		if info.GetCurrentHistoryLength() > 9000 {
			return workflow.NewContinueAsNewError(
				ctx, DPPPassportLifecycleWorkflow,
				passportID)
		}
	}
}

Two arcs. one engine.

ARC A

Core logistics operations

Multi-tenant headless engine for job lifecycle, assignment orchestration, proof of movement, and settlement intents. Four job archetypes. Six composition patterns. Built for NE India — low connectivity, broken roads, human porters, vehicle breakdowns mid-route. If it survives here, it survives anywhere.

4 archetypes · 6 compositions · sub-100ms API

ARC B

Digital Product Passport

EU ESPR-ready. Textiles DPP mandate 2028. GS1 EPCIS 2.0 native from day one. Long-lived product lifecycle workflows that survive years of ownership transfer, audit cycles, and end-of-life — using Temporal for durable orchestration.

Textiles 2028 · EPCIS 2.0 native · Catena-X compatible

Technical design

Headless. API-first. Built to be consumed.

koto7 exposes a GraphQL-native interface. Tenants integrate once and consume any job archetype, any composition pattern, any DPP workflow.

[01]

GraphQL native

gqlgen. Schema-first, Go-native GraphQL. Tenant context enforced in every resolver. Mutations map to domain commands — never direct DB writes. DataLoader from day one. No N+1.

[02]

Temporal orchestration

Temporal Cloud for production. Three workflow shapes: fast event ingest (seconds), batch chain commit (cron), DPP passport lifecycle (years). EU namespace isolated for data residency.

[03]

Tiered ledger (adapter)

Policy engine routes deterministically: private sidechain for logistics events, public root chain for DPP certification finality. People job data never touches a chain — hard constraint, not config.

GS1 EPCIS 2.0 GS1 Digital Link Catena-X compatible EU ESPR Textiles DPP 2028 Multi-tenant PaaS GS1 EPCIS 2.0 GS1 Digital Link Catena-X compatible EU ESPR Textiles DPP 2028 Multi-tenant PaaS

Documentation as product

Architecture contract

System shape, workflow boundaries, and integration paths are documented as engineering contracts, not slideware.

Guardrails and invariants

Tenant isolation, policy constraints, and chain data boundaries are explicit and versioned.

ADR history

Every meaningful architecture decision has rationale, alternatives, and scope consequences attached.

Schema-first GraphQL · Temporal workflows · Tenant invariants documented · Error catalog versioned

Start with overview

The testbed

“If it works in Northeast India, it works in any supply chain.”

koto7's anchor deployment is 7 Hills Nexgram Limited — a digital-first essential services group operating across power, education, health, and logistics in Northeast India. The region has some of the lowest connectivity, highest terrain variability, and most fragmented last-mile logistics in Asia. Operating here produces a battle-hardened engine. The difficulty is the asset.

> route: Guwahati → Shillong → Aizawl
> distance: 670km
> terrain: mountain passes, seasonal closures
> connectivity: intermittent 2G
> job_kind: freight | hybrid | porter
> status: OPERATIONAL

> currently: NE India deployment · exporter DPP pilot in progress · EU platform conversations open

Who is building this

Built at the intersection of two worlds most teams only see one side of.

koto7 is being carved out of 7 Hills Nexgram Limited as an independent technology company. Our CTO studied Distributed Software Systems at TU Darmstadt and has spent years operating digital infrastructure across Northeast India. We are building at the intersection of emerging market logistics complexity and EU regulatory compliance — NE India as testbed, Indian exporters impacted by EU DPP mandates as the first integration cohort, and EU DPP platforms as the integration layer for business continuity.

Get in touch

Partner. Integrate. Build together.

We are in active conversations with EU DPP platform providers and Indian exporters preparing for EU compliance. If you are building in this space — reach out.

For exporters, this is compliance-as-business-continuity infrastructure, not a reporting afterthought.

EU DPP platforms Logistics tech providers Indian exporters to EU