§ Onboarding

One data contract.
Two ways to get there.

PropTector runs on one data contract. Versioned, documented, platform-agnostic. You just have to land data in it.

§ 01 · Why one contract

One shape of data. Every customer on the same engine.

01 · Portable

Your pipeline is yours.

The contract is public and versioned. If you ever leave, the data flow still works, pointed somewhere else.

02 · Uniform

Every customer on the same engine.

Improvements ship to everyone at once. No bespoke forks rotting in your instance.

03 · Auditable

No hidden integration layer.

Validator runs locally. Schema is published. You see exactly what goes in and what PropTector sees.

§ 02 · Two onboarding paths

Build it yourself, or engage our dedicated partner.

Same endpoint, same spec, same validator. The only question is who ships the integration.

Path 01 · Self-Serve

You build it.

You have engineering in-house and want to own the pipeline. We hand over the spec, your team ships, the validator tells you the moment data conforms.

What's includedPublished spec, JSON schemas, sample payloads, local validator, reference client.
Time to go-liveClient-paced · typically 2–4 weeks
Cost structureNo extra onboarding charge. The standard PropTector setup fee still applies.
Who owns itYour engineering team.
Not sure?

Not sure which tier fits?
Book a 30-minute call and we'll tell you straight.

We look at your stack, figure out the fastest path to the contract, and send a written recommendation in 48 hours.

Book a 30-minute call