Skip to main content
Follow the two simple administrative steps below to authenticate your users and launch full-featured accounting on your domain (e.g. accounting.mySaaSplatform.com). This approach is best for fast-moving organizations that want to get to market quickly (up to 1000 businesses) and start collecting GTM/acquisition data to further build the case for an embedded accounting roadmap. Typically, after your GTM team gets 1000+ businesses on Tight Ready-to-Launch Accounting, your product team will likely opt to augment your core product by fully embedding accounting user experiences into it.

​
Configure your SSO/authentication mechanism

​
Use your existing identity provider (zero developer effort)

If you use Auth0, AWS Cognito, Okta, or Stytch, this is the authentication mechanism you should use.
You can configure your existing identity provider’s JWKS path, by following Tight’s user provisioning with existing identity provider instructions.

​
Or, provision users with custom code (one developer day)

If you’re not using an existing identity provider of if you simply prefer a custom integration, you can provision Tight user accounts using the Tight API.

​
Route your user to the Ready-to-Launch app

If you are using an existing identity provider, contact the Tight team for the URL that you should redirect your user to. If you are using custom code to authenticate your user with the create company endpoint, the response on this endpoint contains the readyToLaunchUrl that you can simply redirect your user to.

​
Configure your custom domain

By default, the Ready-to-Launch website URL is hosted on tight.com (e.g. https://mySaaSplatform.prod.rtl.tight.com). If you would like to change it to your own custom domain (e.g. https://bookkeeping.mySaaSplatform.com), you can do so by following the steps below:
  1. Specify your Custom Bookkeeping domain (e.g. https://bookkeeping.mySaaSplatform.com)
  2. Specify your existing login page URL (e.g. https://app.mySaaSplatform.com/login)
  3. Create CNAME Record on your DNS provider
    1. Go to your DNS provider’s website (e.g. GoDaddy or Cloudflare).
    2. Go to the “DNS” section
    3. Add a CNAME record for your Bookkeeping custom domain:
      1. Give the CNAME a “Name” value based on the first part of your custom domain, e.g. if your custom domain is bookkeeping.mySaaSplatform.com, use bookkeeping.
      2. Give the CNAME a “Data” value based on Tight’s default RTL URL for your platform (e.g. mySaaSplatform.prod.rtl.tight.com)
    4. Add a CNAME record for your new bookkeeping SSL certificate:
      1. Give the CNAME a “Name” value provided to you by your Tight CSM
      2. Give the CNAME a “Data” value provided to you by your Tight CSM