Loading page…
Loading page…
Keep mapping and validation in your application. Use Cloud to manage which importer configuration is active, who can import, and where accepted batches are delivered.
Publish importer versions so each session uses a known schema and destination.
Your authenticated backend authorizes users with scoped, short-lived sessions.
Relay accepted batches to an approved HTTPS endpoint. Your receiver verifies signatures and handles repeated batch IDs.
Hosted pricing and self-service production activation are not available yet. The local importer does not require a Cloud subscription.
Understand the data flow
File → browser → your handler
Mapping and validation run on-device. Your application chooses whether to send the accepted records onward.
File → browser → relay → your endpoint
Accepted batches transit the Cloud relay. It stores configuration and operational metadata, rather than imported row payloads.