Skip to main content

​
Bring Your Own Storage (BYOS)

Pulse allows Enterprise customers to store their extraction artifacts in their own cloud storage infrastructure instead of Pulse’s managed storage.
Custom storage is available for Enterprise customers. Email support@trypulse.ai to enable this feature.

​
Why Use Custom Storage?

Data Sovereignty

Keep all extracted data within your own infrastructure and geographic boundaries.

Compliance

Meet regulatory requirements like HIPAA, SOC 2, or GDPR by controlling where data is stored.

Integration

Seamlessly integrate extracted data with your existing data pipelines and workflows.

Cost Optimization

Leverage existing storage contracts and optimize costs across your organization.

​
Supported Providers

Pulse supports the following cloud storage providers:
ProviderAuthenticationSetup Guide
Amazon S3IAM Role (AssumeRole)AWS S3 Setup
Azure Blob StorageConnection String or SAS TokenAzure Blob Setup
Google Cloud StorageService Account JSONGCP Setup

​
How It Works

When you enable custom storage:
  1. Configure - Set up your cloud storage and provide credentials to Pulse
  2. Test - Verify connectivity and permissions with the Test Connection feature
  3. Enable - Toggle on custom storage to start using it
  4. Use - All new extractions are automatically stored in your bucket/container

​
What Gets Stored

Each extraction creates the following artifacts:
ArtifactDescription
result.jsonComplete extraction results including markdown, structured data, and metadata
original_file.*The original uploaded document (PDF, image, etc.)
Artifacts are organized in a predictable structure: 
{base_path}/orgs/{org_id}/extractions/{job_id}/artifacts/
├── result.json
└── original_file.pdf

​
Security

Pulse uses AWS STS AssumeRole with an External ID. No long-lived credentials are stored in Pulse - we obtain temporary credentials on-demand.
Credentials are encrypted at rest in Pulse’s database using AES-256 encryption.
Service account keys are encrypted at rest. Use key rotation and audit logging for enhanced security.

​
Getting Started

  1. Check your plan - Custom storage is available for Enterprise customers
  2. Choose a provider - Select AWS S3, Azure Blob, or GCP Cloud Storage
  3. Follow the setup guide - Complete the provider-specific configuration
  4. Configure in Pulse - Add your storage credentials in Settings > Storage
  5. Test and enable - Verify the connection and enable custom storage

AWS S3

Set up IAM role for S3 access

Azure Blob

Configure Azure Blob Storage

GCP Storage

Set up GCP Cloud Storage

​
API Reference

For programmatic storage configuration, see the Storage API Reference.