HuraSeedcontact@huraseed.eu

[ Realistic sandbox data in minutes • GDPR-safe masking • Processed in the EU ]

Realistic Sandbox Data.
Zero Production Risk.

HuraSeed gives Salesforce Administrators and Engineering teams the power to extract, mask, and seed realistic production data into sandboxes and scratch orgs. Parent-child hierarchies and required lookups arrive intact, and records stream through memory: no customer field values are ever written to storage.

Opens a pre-filled email. No data is stored by this site.

§ 01 — For Administrators

Built for Salesforce Administrators

  1. Automated Relationship & Lookup Integrity

    Eliminate hours of post-refresh CSV VLOOKUP gymnastics. HuraSeed resolves your schema dependencies automatically—preserving parent-child hierarchies across Accounts, Contacts, Opportunities, Cases, and custom objects. Every required lookup points at a seeded record, and references to records outside the job are cleared, never left dangling.

  2. Format-Preserving, Locale-Aware Masking

    Ensure test records look and behave like real data without exposing personal details. Generates checksum-valid IBANs (ISO 13616 mod-97) and locale-aware names with native European diacritics (ä, ö, ü, ß) so your validation rules, formulas, and flows run without false errors.

  3. Hard Production Safeguards

    Production is never a target. Every target org must identify itself as a sandbox or scratch org, checked when it is connected and again when each job starts. Anything else is refused before a single record is written.

§ 02 — For Developers & DevOps

Built for Developers & DevOps Teams

  1. Directed Acyclic Graph (DAG) Resolution

    Orders every object by its lookups and loads parents before children. Polymorphic lookups are routed to the right object by record ID, and self-references and cycles are inserted first and patched in a second pass—all in one run, with no Apex installed in your org.

  2. Bulk API 2.0 Streaming

    Jobs run on BullMQ worker queues. Large object trees stream org-to-org through Salesforce Bulk API 2.0, which keeps API call consumption low.

  3. No Field Values at Rest

    Records are extracted, masked, and loaded in memory, one batch at a time. Field values are never written to disk, staging tables, or analytics databases. Only record IDs are kept during a job, so lookups connect correctly.

§ 03 — Specification

Technical Specifications

Use cases
Sandbox seeding, UAT preparation, scratch org hydration
How it runs
Inside Salesforce as a Lightning app (Canvas). Nothing to install on your computer, no browser extension.
Source orgs
Production or any sandbox
Target orgs
Scratch orgs, Developer, Developer Pro and Partial Copy sandboxes. Production is blocked by a hard safeguard.
Subsets
Relationship-aware subsets (in pilot)
Masking
Default-deny: every text field is masked unless you choose to keep it; classified fields are always masked. Locale-aware values (names with ä/ö/ü/ß, checksum-valid IBANs). Consistent within a job: the same value masks the same way on every object.
Auth & transfer
Salesforce Bulk API 2.0. OAuth 2.0 with PKCE via an External Client App, with refresh token rotation.
Processing location
Customer data is processed in the EU (Ireland)
Encryption
OAuth tokens encrypted with AES-256-GCM. TLS encryption in transit.
Data retention
No customer field values stored. Records stream through memory. Record IDs are kept temporarily during a job so lookups connect correctly, then deleted. For records that fail to load, the record ID, error code and field names are kept for the job report.
Requirements
Salesforce edition with API access (Enterprise, Unlimited, Performance or Developer)