- Getting Started
- Using Hevo
-
Pipelines
- Familiarizing with the Pipelines UI
- Pipeline Concepts
- Working with Pipelines
- Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Mapping a Source Event Type with a Destination Table
- Mapping a Source Event Type Field with a Destination Table Column
- Resizing String Columns in the Destination
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Bulk Actions in Schema Mapper
- Auto Mapping Event Types
- Creating File Partitions for S3 Destination through Schema Mapper
- Schema Mapper Compatibility Table
- Sources
- Destinations
- Transform
- Activate
- Concepts and Reference
- Account Management
- About Hevo
- FAQs
-
Release Notes
- Release Version 1.57 (22-Feb-2021)
- Release Version 1.56 (09-Feb-2021)
- Release Version 1.55 (25-Jan-2021)
- Release Version 1.54 (12-Jan-2021)
- Release Version 1.53 (22-Dec-2020)
- Release Version 1.52 (03-Dec-2020)
- Release Version 1.51 (10-Nov-2020)
- Release Version 1.50 (19-Oct-2020)
- Release Version 1.49 (28-Sep-2020)
- Release Version 1.48 (01-Sep-2020)
- Release Version 1.47 (06-Aug-2020)
- Release Version 1.46 (21-Jul-2020)
- Release Version 1.45 (02-Jul-2020)
- Release Version 1.44 (11-Jun-2020)
- Release Version 1.43 (15-May-2020)
- Release Version 1.42 (30-Apr-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
Infrastructure Security
Hevo follows strict policies to maintain a secure infrastructure:
- All connections to Hevo UI are encrypted through HTTPS and any attempt to connect with Hevo UI over a non-encrypted connection is redirected to HTTPS.
- All API calls to Hevo services are encrypted through HTTPS and any attempt to connect with Hevo services over a non-encrypted connection is redirected to HTTPS.
- Hevo’s complete infrastructure resides in AWS VPC with strict firewall controls over incoming and outgoing traffic.
- All services persisting customer data are deployed on AWS private subnets.
- Access to all resources in Hevo’s infrastructure is limited to Hevo’s VPN. Only technically qualified staff in Hevo is allowed to access these resources.
- We follow industry standard practices to secure our servers and databases.
Last updated on 16 Feb 2021
Was this page helpful?
Thank you for helping improve Hevo's documentation. If you need help or have any questions, please consider contacting support.