§ Onboarding

One data contract.
Two ways to get there.

PropTector runs on a single canonical data format. Versioned, documented, platform-agnostic. Your stack doesn't have to match ours. You just have to land data in the contract.

§ 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 PropTector, the data flow you built still works. Pointed somewhere else. No lock-in, no black box.

02 · Uniform

Every customer on the same engine.

Improvements ship to everyone at once. No bespoke forks rotting in your instance. The platform gets sharper for you because it's getting sharper for everyone.

03 · Auditable

No hidden integration layer.

The validator runs locally. The schema is published. You can see exactly what's going in and exactly what PropTector sees. No magic translator in the middle.

§ 02 · Two onboarding paths

Build it yourself, or engage our dedicated partner.

Same endpoint, same spec, same validator either way. The only question is whether your team ships the integration or our dedicated data partner does.

Path 01 · Self-Serve

You build it.

You have engineering in-house and would rather own the pipeline yourselves. We hand over the spec; your team ships the integration; our validator tells you the moment the 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'll look at your existing stack, figure out the fastest path to canonical data, and send a written recommendation in 48 hours.

Book a 30-minute call