Skip to content

Agencies & system integrators

One platform.
Many client projects.

Deliver customer data and identity resolution projects with separate environments, repeatable setup practices and support planned around each client.

Become a partner Explore the delivery workflow

Illustrative client setup

Client A
ProductionTest
Dedicated workspace databases
Client B
ProductionRegional project
Dedicated workspace databases

One client can have multiple workspaces.

One platform. Multiple clients. Clear separation.

Design each client environment deliberately.

A workspace has its own database, connections and Customer Model. Plan the deployment and access boundaries for each client, including production, test and any additional environments.

Match the client’s stack

Use the client’s PostgreSQL or Snowflake warehouse, or discuss the proposed Free and Starter paths with Krenalis-managed PostgreSQL.

Separate data and operations

Define workspace databases, credentials, access and operating responsibilities for each engagement. A workspace is not automatically an agency tenant.

Agree on ownership early

Set out who controls the database, credentials, configuration and ongoing operations before delivery starts.

Repeatable delivery

Build a practice around customer data.

Reuse your own setup patterns and delivery checklists, then configure and validate each client’s data separately.

  1. 01

    Start from your delivery template

    Define the Customer Model, deployment checklist and responsibilities for the engagement.

  2. 02

    Connect client data

    Map CRM records, website events and other sources to the client’s workspace.

  3. 03

    Configure identity rules

    Select identifiers, priorities and property sources appropriate to that business.

  4. 04

    Validate and activate

    Check representative matches and non-matches, then connect the intended destinations.

  5. 05

    Scale and support

    Document the setup, agree on ongoing operations and expand the scope as needed.

Delivery templates here describe your reusable project practice, rather than a promised built-in template or tenant management feature.

Service opportunities

Turn the platform into a client outcome.

Customer data modeling

Help clients define useful customer attributes, events and identifiers.

Integration projects

Connect source systems, build mappings and configure destinations.

Identity resolution setup

Design, test and refine matching rules against client data.

Onboarding and enablement

Prepare environments, document the setup and train the client team.

Analytics and Customer AI

Make consistent profiles and customer history available to downstream applications.

Ongoing operations

Offer agreed monitoring, maintenance and data services as part of your engagement.

Your clients keep control

Build a relationship.
Keep the data accessible.

With BYOW, customer data is stored in the client’s chosen workspace database. Use clear agreements for access, documentation and operational handover.

Any transfer between operators or hosting arrangements needs a technical and contractual review. Define that process before promising portability.

Client ownership

Agree who owns and administers the database and connected accounts.

Documented delivery

Record identifiers, priorities, mappings, dependencies and operating procedures.

Planned handover

Agree how the client or another operator can take responsibility for the setup.

Partner conversations

Shape the model around the engagement.

Talk to us about partner or reseller options, dedicated support and professional services. Program structure, eligibility, commercial terms and availability are still being defined.

Discuss licensing before offering a hosted service to third parties. Partner discussions do not change the current licence terms.

Review the licence policy

Bring us a client scenario.

Share the number of clients and environments, data sources, deployment preferences and the services you want to deliver.

Discuss a partnership