DEVELOPERS / INTEGRATION GUIDE

Start with one data flow.

Understand the boundary with a runnable local example. Then define the API contract, permissions and failure behavior for a provisioned pilot.

01 / EXPLORE THE MECHANISM

Originals stay.
References travel.

Copy this JavaScript example into a file and run it with Node.js. It prints the model context using fixed, fictional mappings.

EXPECTED OUTPUTcustomer: person_7f2a
email: email_9b4c
plan: Business
request: Help me change my plan

This learning example is separate from a production integration. Request the current API contract and environment details from the team.

boundary-example.mjs
// Local learning example — Node.js 18+; no packages or API calls.
// Fixed fictional mappings illustrate the boundary, not cryptography.
const source = {
  customer: "Alex Morgan",
  email: "alex@example.com",
  plan: "Business",
  request: "Help me change my plan"
};
const mappings = {
  customer: "person_7f2a",
  email: "email_9b4c"
};
const modelContext = {
  customer: mappings.customer,
  email: mappings.email,
  plan: source.plan,
  request: source.request
};
if (JSON.stringify(modelContext).includes(source.email)) {
  throw new Error("Original email crossed the example boundary");
}
console.log(JSON.stringify(modelContext, null, 2));
// Production: replace fixture mappings with a provisioned vault,
// authenticate callers and enforce retrieval permissions server-side.

Run with node boundary-example.mjs. The fixed fixture is fully local; it does not tokenize real data or call Provyn.

03 / FROM EXAMPLE TO PILOT

A clear first milestone.

PREPARE

Bring one synthetic record.

List the applications, fields, recipients and one query or operation that must keep working.

PROVISION

Agree on the contract.

Request access, API documentation, authentication requirements and the supported client for your environment.

EVALUATE

Test the difficult paths.

Check denied access, invalid input, retries and outages. Measure useful output as well as data protection.

START WITH ONE WORKFLOW

Map your first data workflow.

In a 30-minute architecture session, identify the fields to protect, the systems involved and the checks for a pilot.

Book a 30-minute demoOpens the booking form on provyn.cloudsales@provyn.cloud