Deep-dive on the Next Gen Platform. Join the Webinar!

Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Working with Node.js
      • Troubleshooting Node.js Apps
      • Node.js Behavior in Heroku
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Working with AI
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Add-ons
  • All Add-ons
  • DQE One
DQE One

This add-on is operated by DQE SOFTWARE

Deduplication, Duplicate, Data Quality & Dedupe Management for Salesforce.

DQE One

Last updated April 04, 2025

Table of Contents

  • Prerequisites
  • Sample App with Heroku Deploy
  • Provisioning the Add-on
  • Installation
  • Environment Variables
  • Deploy the Heroku App
  • Launch DQE One
  • Removing the Add-on
  • Support

DQE One is an add-on to deduplicate, clean, and qualify your Heroku Postgres, Salesforce, and Data Cloud databases. The system operates as a microservice. Our managed package on Salesforce installs the interface, allowing you to launch and customize each process for deduplication, cleaning, and qualification.

This article shows how to install and manage the add-on. For instructions on how to use DQE One Server, see our documentation.

Prerequisites

Before provisioning the add-on, install the Heroku CLI.

Log in to your Heroku account and follow the prompts to create a SSH public key:

$ heroku login

Sample App with Heroku Deploy

Install this sample Python app that automatically adds the buildpacks required for the add-on.

Deploy

If you want to create an app on your own, follow the instructions in Install Buildpacks.

Provisioning the Add-on

Reference the DQE One Elements Page for a list of available plans and regions.

You can attach DQE One Server to a Heroku application via either the CLI:

$ heroku addons:create dqe-one-server:v1-1 --app your-app-name

Or by clicking Install DQE One in the Elements Marketplace.

Installation

Add-on

You must install the Heroku Key-Value Store and CloudAMQP add-ons before using DQE One:

$ heroku addons:create heroku-redis:mini --app your-app-name

$ heroku addons:create cloudamqp:lemur --app your-app-name

Buildpacks

After provisioning the add-ons, install these buildpacks:

You must install these buildpacks in the exact order.

  • DQE One buildpack
  • Heroku Python buildpack

Install the DQE One buildpack:

$ heroku buildpacks:add --index 1 dqe-software/dqe-one-buildpack --app your-app-name
Buildpack added. Next release on dqe-one will use dqe-software/dqe-one-buildpack.
Run git push heroku main to create a new release using this buildpack.

Install the Heroku Python buildpack:

$ heroku buildpacks:add heroku/python --app your-app-name
Buildpack added. Next release on dqe-one will use dqe-software/dqe-one-buildpack.
Run git push heroku main to create a new release using this buildpack.

Environment Variables

To complete the deployment, you must put your DQE license into the DQE_ONE_SERVER_LICENSE variable.

Deploy the Heroku App

Clone the repository with git:clone to clone your app source code to your local machine. Then create a .python-version file, containing “3.11.11” in it:

$ heroku git:clone -a your-app-name
$ cd your-app-name

Unix

$ echo "3.11.11" > .python-version

Windows Powershell

$ "3.11.11" | Out-File -Encoding ascii -NoNewline ".python-version"

Make some changes to the code you just cloned and deploy them to Heroku using the git commands:

$ git add .
$ git commit -am "first deploy"
$ git push heroku master

Launch DQE One

The DQE One buildpack contains a Procfile that creates two dynos that you must start:

$ heroku ps:scale worker=1 web=1 --app your-app-name
Scaling dynos... done, now running worker at 1:Hobby, web at 1:Hobby

Removing the Add-on

You can remove DQE One Server via the Heroku CLI:

This destroys all associated data and you can’t undo it!

$ heroku addons:destroy dqe-one-server --app your-app-name

Support

Submit all DQE One support and runtime issues via one of the Heroku Support channels. For other questions or suggestions, email us at support@dqe-software.com.

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Zara 4 Draxlr | Analytics for SQL Databases

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices