When should you consider it?
Consider it when model logic must remain a customer-controlled, versionable engineering artifact, while teams need shared access, IDE and agent authoring, scheduling and traceable execution. Download complete project logic; models using only CE-supported functions can also run in CE.
Editorial fit assessment based on the sources below.What are the limits?
CE portability applies to the shared, CE-supported model scope. EE-only functions such as Kafka nodes, Enterprise ML and advanced nodes require EE. CE does not reproduce Platform governance or provenance services and has different runtime optimizations. Confirm IDE versions, connectors and replay conditions for the exact workload.
Customer-owned engineering artifacts
The customer owns the model and project logic: XML models, scripts, rules and supporting project files can be inspected, edited and versioned. The full project can be downloaded, including the project state associated with a task. This preserves the logic required to understand a scenario and maintain it outside a browser-only authoring workflow.
ReferenceRule Sets and learned generators in one model
Rule Sets express explicit business constraints and transformations. The documented rule pipeline separates source constraints, ordered mappings and target constraints; conditional structures define output shape. Enterprise ML generators provide learned distributions that the model can consume through ml:// and combine with explicit field logic. Teams can keep required business cases explicit while using learned data where it serves the scenario. Learned output should be validated against the required business invariants.
Reference · Reference 2 · Reference 3A concrete exit path to CE
CE and EE share the model language. A downloaded project using only CE-supported elements, generators, sources and targets can execute the same model in CE without a rewrite, with compatible engine versions, configuration and resources, and available dependencies, inputs and target services. Kafka, Enterprise ML and other EE-only nodes remain edition boundaries. CE has Python multiprocessing; EE adds a separately optimized engine and additional throughput optimizations. Model portability preserves customer logic; Platform access controls, task orchestration and provenance are Enterprise services. For CE-compatible models, the model logic is not tied to an EE runtime.
ReferenceSeparate EE core and Platform ownership
EE and CE share a model language and have separate execution engines. The EE core executes Enterprise data workloads. Platform services manage project workspaces, permissions, APIs, workers, scheduling and execution records.
ReferenceGovernance belongs to the Platform
The Platform manages project access, user administration, collaboration and execution. Developers and agents work on the same customer-owned project, within the permissions of that project. Scheduling and task records remain governed by the Platform regardless of the authoring interface.
ReferenceRelational subset planning and source-row selection
In Database Workbench, select table and column scope, then run Plan Subset. The Platform analyzes foreign-key dependencies and automatically adds required tables to the model scope. Review the plan before creating and running a model. SQL selectors separately define which source rows an extraction workflow reads. Table-scope closure and row-level extraction are different operations; validate the combined result against your schema and relationships.
ReferenceBrowser IDE and IDE extensions
The Platform provides browser-based authoring and an extension workflow for VS Code, Kiro and Google Antigravity. Project files remain in the Platform workspace; hosted language services support completion, diagnostics and hover. Check the documented host and version qualifications before rollout.
ReferenceDeveloper and agent execution workflow
Developers can author and start generation through the Platform and its IDE integration. Agents can connect through project-scoped MCP. The extension configures access for supported IDE agents; standalone clients such as Codex and Claude Code use the documented OAuth or project-token connection path.
ReferenceProvenance and execution evidence
The task record connects execution with its actor, task ID, timestamps, status, logs, previews and output artifacts. A project snapshot from the time of execution can be downloaded; Git-connected projects can retain task-specific project state. These records make model, execution and result traceable for review.
ReferenceGenerate, Extract & Transform, Learn, Combine
Generate creates explicit business scenarios. Extract & Transform selects existing records and applies field rules. Learn uses persisted Enterprise ML models. Combine brings these mechanisms together in a project: source values, transformations, rule-defined cases and learned distributions can serve different parts of the same data scenario.
ReferenceThe Enterprise product combines an EE execution core with Platform services. CE is a separate installable developer package. A capability or proof from one runtime does not automatically establish it for the other.
DATAMIMIC CEWhich capabilities are documented?
Documented means a cited vendor source describes this scoped capability. Not verified means the reviewed evidence cannot establish it. Neither is a hands-on test result.
How is it deployed and licensed?
Enterprise deployment on-premises using supported containers or Helm, with separate backend, workers, scheduler and task monitoring. The vendor also documents air-gapped environments. The EE core executes data workloads; Platform services own projects, access and execution management.
Commercial Enterprise product. No current public list price was found; scope and pricing are agreed with the vendor. CE is a separately distributed MIT-licensed developer package.
Sources and scope
- DATAMIMIC documentation home
Platform authoring, project, execution and operational documentation.
Source checked: 2026-10-01 - rapiddweller/datamimic repository
Publisher-documented distinction between CE and the separate EE execution engine, Platform governance, pseudonymization and audit/provenance functions.
Source checked: 2026-10-01 - Upgrade your models from DATAMIMIC 3.5 to 4.0
Exact replay boundary; requires same engine version, complete deterministic inputs, explicit seed, execution topology, deterministic serialization and ordering; ML is excluded; date behavior depends on the seeded reference clock.
Source checked: 2026-10-01 - Date and Time Generation
Relative date windows use a runtime clock anchor; seeded execution uses deterministic runtime clock, while unseeded execution reads live clock.
Source checked: 2026-10-01 - Platform features
Enterprise generation and de-identification workflows, collaboration, access control and operational execution management.
Source checked: 2026-10-01 - DATAMIMIC product page
Enterprise positioning, on-premise deployment and vendor contact; does not publish a list price.
Source checked: 2026-10-01 - Element <ml-train>
Trains a versioned tabular model from project data for learned distributions; a separate workflow from deterministic rule-based generation.
Source checked: 2026-10-01 - Source reference
Documented file/database/message sources, selection and chained memstore workflows for source-driven extract/transform and staged combination.
Source checked: 2026-10-01 - Target attribute
Multiple target values may combine output formats or environments.
Source checked: 2026-10-01 - Generation model reference
Model-driven generation syntax and execution controls.
Source checked: 2026-10-01 - Enterprise system architecture
Separate backend, workers, scheduler, task monitor and shared operational services.
Source checked: 2026-10-01 - Project user access management
Platform-owned project membership and access administration.
Source checked: 2026-10-01 - DATAMIMIC IDE extension
Remote project workspace, supported IDE hosts/version qualifications and hosted language services.
Source checked: 2026-10-01 - Project-scoped MCP client connection
IDE and standalone agent clients, OAuth, tokens and project scope.
Source checked: 2026-10-01 - Task execution and provenance
Actor, task identity, timestamps, logs, output artifacts and task-time project snapshots.
Source checked: 2026-10-01 - DATAMIMIC vs Delphix: source selection and transformation example
Vendor-published CE 4.3.0 example: SQL range selection, explicit field transformations and target writing; edition-scoped four-path explanation. The reported execution was not independently repeated in this comparison.
Source checked: 2026-10-01 - Iterate source traversal
Source records and parent context for explicit child transformations and target generation.
Source checked: 2026-10-01 - Relational Database View and subset planning
Selected table/column scope, automatically applied required foreign-key table closure, review gate and distinct model-creation outcomes; not a universal row-copy benchmark.
Source checked: 2026-10-01 - Workbench model planning
Reviewed dependency planning before model configuration; generated XML is saved and opened for deliberate composition and execution.
Source checked: 2026-10-01 - Structured data and rule pipelines
Explicit constraints, ordered mappings and conditional nested structures.
Source checked: 2026-10-01 - Project editor and language services
Project files, XML authoring and hosted LSP.
Source checked: 2026-10-01
What should you verify in a proof of concept?
- Your database version, schema constraints and target formats.
- The exact product, edition, deployment and license entitlements.
- Your business assertions and the meaning of repeatability for your output.
- A failed run, cleanup and a repeat run on controlled inputs.