dbLauncher for Access

Front-end deployment service for Microsoft Access based solutions

Learn More

About the dbLauncher

The dbLauncher for Access provides a robust and consistent deployment experience for all your Microsoft Access applications.

Access Front-Ends Benefit From Running on the Local Machine

Copying Access the front-end down to the local users computer will minimize network traffic and all but eliminate corruption, but can be a burdensome task. The dbLauncher is a service that greatly simplifies pushing new versions of your Access front-ends to each workstation. The standalone dbLauncher client runs on each user's computer and performs the following:

  • Authenticate the user with Microsoft OAuth 2.0.
  • Present the user with a list of applications they have permission to use.
  • Download the applications Zip file from Azure if the current Zip has not been downloaded.
  • Unzip the application files and start Access with the configured settings.

All the configuration setting for an application, its groups and users, can be managed from the client by users with administrative rights. Updating an application is as simple as copying any updated files into the deployment Zip file and uploading from the client to Azure.

Overview of a dbLauncher deployment

Key Features

Some of the dbLauncher features include the following:

Microsoft OAuth 2.0 User Authorization

Application user identities are authenticated with Microsoft OAuth 2.0, eliminating separate passwords, and minimizing user sign-ins.

Update Notifications

Whenever your application has an update available, the end users will receive a popup notification.

Encrypted Azure File Storage

All deployment files are encrypted at rest in an Azure file container. Storage location can be selected from several Azure regions.

Easy Administration

Application settings can be managed right from the client application. Updating an application is a simple as uploading a Zip file.

32-bit and 64-bit Office

Automatically detects 32-bit or 64-bit installations of Office and downloads the corresponding files for a compiled application.

Trusted Location

The dbLauncher always make sure applications are run from a trusted location.

Desktop Shortcuts

Users can create desktop shortcuts for frequently used applications and the admin can force an application to always start with the dbLauncher, ensuring the user always has the most current front-end.

Per User Deployment

Front-end files are downloaded when there is an update, deployed to each user’s computer and then run locally. Option to give the user a fresh copy of the application on each launch.

Maintenance Mode

Maintenance Mode will prevent all users from starting an application. It will also prompt any users currently running the application to exit.

Frequently Asked Questions

  • Once you create an account, you can configure and deploy your first application in about 10 minutes.

    - Create an owner account on dbLauncher.com
    - Add one or more organizations
    - Add a configuration for each application you want to deploy and upload a Zip file with the required front-end files
    - Assign those applications to groups that have rights to run the application
    - Assign user to the appropriate groups
    - Install the dbLauncher Client on each users machine (it’s a standalone EXE)

    That’s all!

    To deploy a new version, simply update the front-end files in the Zip and upload it from the client

  • Yes, your clients will always need an active internet connection so they can be authenticated by Microsoft OAuth 2.0.

  • OAuth 2.0 is the industry-standard protocol for authorization, which allows a user’s identity to be validated without creating an account or entering a password. The Microsoft standard of OAuth is used, which allows a user to sign in with any Microsoft account.

  • Yes, all front-end files are stored in an encrypted Azure Storage container. The Microsoft Storage service encryption protects your data at rest. Azure Storage encrypts data as it's written to the datacenters, and automatically decrypts it when downloaded. Each Organization files are stored in a separate container and an organization''s files can be stored in any one of the Azure datacenters.

  • An organization is generally going to be a single company or department in a large corporation. Groups and applications can only belong to one organization, but a user can belong to groups, in multiple organizations. If you are an Access developer and have more than one client, each client would be a separate organization.

  • We are still finalizing the cost, but the goal is to make it extremely affordable, like the price of a cup of coffee or a beer, per user per year. See below for more information on our tentative pricing model.

Tentative Pricing

To make the dbLauncher service affordable for clients with a few users as well as ones with hundreds, we are using a token model. When you purchase a block of tokens, at the end of the month, we will calculate the usage and reduce your token balance by that amount. Tokens can be shared across multiple organizations with the same owner. Purchased tokens do not expire, unless there are two years of inactivity. Unused tokens can be refunded, less a small processing fee.

What is a token?

1 Token = 1 month of unlimited applications for 1 user on 1 machine, per organization

For example, if Joe only works from the office on one computer, he will use 1 token per month.

If Sue works from home on her laptop most days, but comes into the office and works once a week on a desktop, she will use 2 tokens per month.

If a user does not launch any applications from a machine during a month, then no tokens are used.

100 Tokens

$0.49 / Token

  • ~ $5.88 - $11.76* /user/year
  • Non-Refundable

500 Tokens

$0.39 / Token

  • ~ $4.88 - $9.76* /user/year
  • Refundable
    (less 100 token processing fee)


$0._ _ / Token

  • Need to deploy to 100 users or more?
  • Contact us for a custom pricing plan.

We expect most end users will consume 1 or 2 tokens a month*

Token Estimator

Estimated monthly or yearly token usage.

Number of Users:

Average Tokens per User:




While we are not quite ready to release the dbLauncher to the general public, we are looking for beta testers.

If you have a Microsoft Access application that you distribute to between 5 and 25 REMOTE users, we would love to hear from you!

Please use the contact form below and tell us a little bit about your application.

(Contact form is currently disabled, please use email instead.)


Seattle, WA


1sseccA 527 1+

1773 222 527 1+

Your message has been sent. Thank you!