Official SOFI platform portal

Test data for delivery.
Live data for consumption.

A decision portal that routes each customer to the right SOFI product: secure, masked delivery environments with Test Data, or governed live-data consumption with Virtualization.

Explore the platformsHow to choose

2

SOFI platforms

1

routing decision

0

routing ambiguity

SOFI CLI builder
platform:Virtualizationsource:erp.customer_360access:governed-live
active operation
Virtualization
[ CLI ][ .JSON ]
1
$
2{
3 "platform": "SOFI Virtualization",
4 "source": "erp.customer_360",
5 "policy": "governed-live",
6 "endpoints": ["SQL", "REST", "MCP"],
7 "status": "published"
8}
SQL view
policy enforced
MCP context
Publishing governed live view...

Connects to the stack you already run

PostgreSQLOracleSQL ServerMongoDBSnowflakeBigQueryRedshiftS3KafkaREST APIsSalesforceDatabricksPostgreSQLOracleSQL ServerMongoDBSnowflakeBigQueryRedshiftS3KafkaREST APIsSalesforceDatabricks
[ 01 / platforms ]

Two platforms for two distinct operating moments.

First identify whether the customer needs secure delivery environments or governed access to live data. Each platform has its own operating path, so requirements do not get mixed.

01

Prepare environments

Test Data

Production-grade datasets for QA, staging, and releases without exposing production.

lightweight clonemaskingrollbackteam branch
View platform
02

Consume live data

Virtualization

A logical layer for BI, APIs, and agents without moving data from source systems.

zero-copySQL + APIssingle policylive lineage
View platform

01 / Prepare environments

SOFI Test Data

Open platform

Delivery and staging environments

SOFI Test Data

Production-grade test environments without copying production.

Provision isolated datasets per team with lightweight snapshots, persistent masking, and reliable restore points. Teams test against useful data without exposing PII or relying on manual copies.

For development, QA, staging, release, and support teams

lightweight clonesmasked PIIrelease rollbackteam-level branching
[ CLI ]
sofi workflow
1
$ sofi clone prod --masked --branch release-42# isolated environment
2
$ sofi bookmark qa release-42-approved# known-good state
3
$ sofi reset qa --to release-42-approved# retest without rebuild
clone.ready
mask.policy=gdpr_lgpd
bookmark.saved
Heavy-copy-free cloningCopy-on-write snapshots bring up large databases without multiplying storage.
Persistent maskingSensitive data is detected and stored masked in the environment delivered to the team.
On-demand branchesEach feature, bug fix, or release can have its own database branch with fork, merge, and reset.
Release bookmarksCapture known-good states and return to them when a test fails or must be repeated.
Pipeline automationClone, mask, snapshot, and reset commands run inside CI/CD without opening tickets.
Auditable permissionsAccess is scoped by environment, database, schema, table, and column, with an operational trail.
Open platformsofitest.dtsofi.com
COW
clones without duplicating TBs
PII
masking before access
Git
branch, bookmark, and reset
runtime signalonline
governancepolicy enforced
auditevent stream active
capability map
CI/CDQAStagingRelease
Controlled refreshRefresh QA and staging in predictable windows with masking policy always enforced.
PII discoveryClassifiers locate sensitive fields even in undocumented legacy databases.
sourceprod snapshot

production-grade data without live-data exposure

controlbranch + bookmark

approved state for repeatable tests

deliveryQA / staging / release

team-ready isolated environments

operational routedelivery path
01
discover
PII map92%
02
protect
mask rules88%
03
release
QA branch96%
policy88%
latency72%
coverage94%
event streamlive
01masking / PII locked
02clone / branch synced
03qa / reset ready
04rbac / team scoped
05audit / bookmark signed
06slo / window protected
07ci / pipeline green
14.2s
window

clone provisioned

0 PII
risk

sensitive fields masked

ready
rollback

bookmark signed

execution trace
policy: GDPR / LGPD / PII enforced
branch: qa-release isolated
reset: approved bookmark available
active signalsmonitored
clone throughput12 VDBs
mask coverage98%
retest windowready
audit.hash: 8f2c-qa-secured

02 / Consume live data

SOFI Virtualization

Open platform

Governed live data

SOFI Virtualization

Multi-source consumption without moving data.

Connect databases, files, APIs, and warehouses into a logical data layer. Publish governed views for BI, applications, and agents under the same security contract.

For data teams, BI, digital platforms, APIs, and AI agents

zero-copySQL + APIsdynamic maskinglive lineage
[ CLI ]
sofi workflow
1
$ sofi connect postgres orders# registered source
2
$ create view customer_360 as select ...# logical contract
3
$ sofi publish customer_360 --rest --sql# governed access
source.linked
view.validated
endpoint.live
Zero-copy federationUnify heterogeneous sources in a logical layer without replicating the origin.
Views as a productModel consumption contracts decoupled from source systems, with joins and rules defined in SQL.
Policy at the perimeterPermissions, dynamic masking, and audit controls are applied before any delivery surface.
Intelligent pushdownFilters, joins, and aggregations are pushed to the source when that reduces cost and latency.
Live lineageEvery column remains traceable from source to consumer, with visible change impact.
Multiple consumption surfacesSQL, REST, OData, GraphQL, and MCP expose the same governed data under one policy model.
Open platformsofivirtualization.dtsofi.com
0 ETL
to publish a view
1 policy
across every channel
Live
consumer-level lineage
runtime signalonline
governancepolicy enforced
auditevent stream active
capability map
SQLRESTODataMCP
Semantic catalogDescriptions, tags, and business context make data assets discoverable.
Governed self-serviceTeams consume data without opening tickets, inside clear limits and contracts.
sourceERP + warehouse

connected sources without replication

contractgoverned view

SQL, REST, and MCP under one model

consumptionBI / API / agents

policy enforced before delivery

operational routeconsumption path
01
connect
sources90%
02
govern
policy86%
03
publish
SQL / API94%
policy88%
latency72%
coverage94%
event streamlive
01policy / RBAC applied
02lineage / impact mapped
03api / contract live
04pushdown / source optimized
05catalog / asset indexed
06cache / policy aware
07query / latency guarded
14ms
latency

guarded query

active
pushdown

source-side execution

live
contract

endpoint published

execution trace
policy: RBAC + masking enforced
lineage: source to consumer mapped
quota: consumer window protected
active signalsmonitored
source pushdownactive
policy cachewarm
endpoint SLOlive
audit.hash: 8f2c-vw-secured

Compare platforms

Which platform matches the operating problem?

Both products share governance and integration standards, but they solve different moments in the data lifecycle. Use the table to route the customer without ambiguity.

Capability
Test Data
Virtualization
Realistic masked test data environments
Thin clones, snapshots, and rollback for QA
Feature-level branching, merge, and reset
Automated PII discovery
Access to heterogeneous sources without moving data
Governed virtual views for SQL, REST, and OData
Real-time lineage from source to consumer
MCP surface for AI agents
Native RBAC, masking, and audit controls
CLI, SQL, and API integration for automation
For delivery and QA

I need realistic masked data for test environments.

Route to Test Data for thin clones, branching, and rollback.

View Test Data→
For BI, APIs, and agents

I need access to data across sources without moving it.

Route to Virtualization for governed views and zero-copy access.

View Virtualization→
End-to-end pipeline

How SOFI operates data
across four controlled steps.

Test Data and Virtualization share the same operational discipline. What changes is the target consumption pattern.

01

Connect

Register sources such as databases, files, APIs, and warehouses in minutes.

  • Ready-to-use connectors
  • Vaulted credentials
  • Automated discovery

02

Protect

Detect PII, apply masking, enforce RBAC, and push policy to the perimeter.

  • GDPR / LGPD
  • Persistent or dynamic masking
  • Immutable audit trail

03

Operate

Test Data isolates delivery teams; Virtualization publishes governed views.

  • Thin clones and branching
  • Virtual views
  • Intelligent pushdown

04

Consume

Developers, QA, BI, applications, and agents consume through the right governed channel.

  • CLI / SQL / REST / MCP
  • SLOs and quotas
  • End-to-end lineage

Enterprise posture

Two operating paths.
One governance discipline.

Test Data and Virtualization are not competing narratives. They cover different stages of the data lifecycle with consistent governance, security, and audit controls across both paths.

LGPDGDPRSOC 2ISO 27001

Privacy

PII is discovered, classified, and masked before data reaches the consumer.

Permissions

RBAC by environment, source, view, table, column, or role, inherited across the platform.

Audit

Operations, access events, publications, and changes are captured in an immutable exportable trail.

Observability

Metrics, lineage, and SLOs per asset expose change impact before it becomes an incident.

SOFI portal

Start with the operating problem.
Open the right product.

Test Data

Delivery and staging environments

Virtualization

Governed live data