TES vs Building Your Own Product Lifecycle Database

Deciding whether to build product lifecycle database in-house or buy a purpose-built solution comes down to one question: do you want to own the data model and compliance surface indefinitely? The Thing Event System (TES), built by Pentatonic, provides the event-sourced infrastructure to make this practical at any scale — one API, one data model, compliance data as a byproduct.

According to Gartner, by 2028, 33% of enterprise software applications will include agentic AI, up from less than 1% in 2024.

2026-03-30

A circular economy decouples economic activity from the consumption of finite resources. It is a resilient system that is good for business, people, and the environment.

Ellen MacArthur Foundation

Define Your Requirements

Before choosing build vs. buy, define your requirements:

// Questions to answer before choosing
const requirements = {
  eventsPerYear: 1_000_000,        // returns + sales + transfers
  complianceTargets: ["EU_DPP", "EPR_FR", "EPR_DE"],
  integrations: ["shopify", "SAP"],
  timeToMarket: "3 months"         // how long can you wait?
};

List the lifecycle events you need to track, the compliance obligations you face (EU DPP, EPR, CSRD), and annual product volume. These are the inputs that determine build vs. buy cost.

Getting Started

Step 1: Estimate the build cost

A custom event-sourced product ledger requires: event store design, schema versioning, projection layer, API design, auth, compliance output layer, and ongoing maintenance as regulations change. Budget 6-12 months of engineering time before you track your first product.

// Rough estimate of custom build scope
const buildScope = [
  "Event store (Postgres/EventStoreDB): 4-6 weeks",
  "Schema versioning + projections: 3-4 weeks",
  "REST/GraphQL API layer: 4-6 weeks",
  "Auth + multi-tenant isolation: 2-3 weeks",
  "EU DPP output format: 4-8 weeks (spec changes often)",
  "EPR reporting by country: 2-4 weeks per country",
  "SDK + documentation: 4-6 weeks",
  // Total: ~6-12 months, 2-3 engineers
];

Step 2: Connect TES and compare

With TES, you skip the build phase entirely. Install the SDK, start emitting events, and get compliance outputs from day one.

// Time to first tracked product with TES:
npm install @pentatonic/tes   // 30 seconds to install

// Time to first EU DPP:
// Emit a passport_issued event — ~10 minutes from zero

According to European Commission, ESPR Regulation 2024/1781, eU Digital Product Passport requirements take effect for batteries in 2027, textiles and electronics by 2030 under the ESPR regulation.

Next Steps

TES is available now. The fastest path forward:

Install: npm install @pentatonic/tes
Get an API key: Book a Demo — Pentatonic will provision your account and walk through your integration.
Track your first product: Three function calls. Under ten minutes.

Full API reference and docs at thingeventsystem.ai.

Why TES Instead of Building It Yourself

TES is not a generic event bus. It is purpose-built for physical product lifecycle tracking, which means the hard parts are already solved:

Concern	Custom build	TES
Data model	Design and version your own event schema	Battle-tested Thing + ThingEvent model, stable versioning
API surface	Design, build, auth, document, maintain	Single REST + SDK API, OpenAPI spec included
Compliance outputs	Write formatters per regulation, update when specs change	EU DPP, EPR reports generated from event log automatically
Audit trail	Append-only log requires careful schema discipline	Enforced by design — the log is immutable
Time to first tracked product	6-12 months	~10 minutes
Compliance output (EU DPP)	Build separately; spec changes frequently	Included; Pentatonic tracks regulation changes
Engineering maintenance	Ongoing; 1-2 engineers minimum	None — managed infrastructure
Integrations	Build per-platform connectors	Shopify, Salesforce, SAP connectors included

The single-API design is a deliberate choice. Every system that touches a physical product — returns portal, warehouse WMS, resale storefront, compliance reporting — uses the same TES endpoint. No fan-out integration problem.

FREQUENTLY ASKED QUESTIONS

What is the real cost of building a product lifecycle tracking system in-house?

Expect 6-12 months of engineering time across event store design, API layer, compliance output formatters, and SDK documentation — before you track a single product. The ongoing maintenance cost is higher as regulations change.

When does it make sense to build product lifecycle tracking yourself?

If your product domain has highly unusual event types that do not map to standard lifecycle events, or if data sovereignty requirements prevent any third-party data processor. For most brands, TES is the rational choice.

What npm package do I use to integrate with TES?

Install @pentatonic/tes from npm: npm install @pentatonic/tes. Initialize with your API key and start emitting product lifecycle events immediately.

How do I comply with the EU Digital Product Passport using TES?

Emit a passport_issued event against any tracked product. TES assembles the EU DPP from the product's event history and returns a hosted passport URL. No separate compliance pipeline is needed — compliance data is a byproduct of tracking operations you should already be running.

What data model does TES use for product lifecycle tracking?

TES uses an event-sourced model. A Thing represents a physical object identified by a stable UUID. ThingEvents record state changes — manufacture, sale, return, grade, resale, recycle. Current state is derived by replaying the event log, which means the full history is always queryable and nothing is ever overwritten.