Getting Started

Before you can get productive with our Saaslets you need to do a few simple things. This guide will take you through the first steps.

1. Add the Saaslets to your app

To add the Saaslets to your app, include the code below and swap YOUR_ELEMENT_REFERENCE for an actual DOM element or selector string that you wish to mount the widget to. You also need to replace PUBLISHABLE_APP_KEY with the publishable app key which you find in the app dashboard.

To learn about other ways of including saaslet.js and how to use it with Angular, Vue, React etc. head over to the saaslet.js reference.

<script type="text/javascript" src=""></script> <script type="text/javascript"> const saaslet = new Saaslet( 'PUBLISHABLE_APP_KEY' ); saaslet.createWidget( "signup-login", "YOUR_ELEMENT_REFERENCE", { companyName: "YOUR_COMPANY_NAME" }, null); </script>

2. Allow Saaslet to share cookies with your domain

Cookies are small bits of information that help you identify a user. They are set by the Saaslet widgets whenever a user logs in and sent to your server whenever the browser issues an HTTP request. BUT: Cookies are strictly limited to a single domain - and for good reasons. To keep things secure, Saaslet needs to be able to share cookies with your domain. There's a couple of ways to do this - please find more here.

3. Connect with Payment Providers

Saaslet is not a payment provider. Instead, we make it super simple to connect existing PayPal and Stripe accounts. Saaslet will synchronize users, plans and payments between them, provide widgets for everything from changing your user's billing address to updating cards, listing invoices, and much more.

4. Verify user requests.

Perfect - you're all set up. Now your user's can register, login, and pay via Saaslet's. But how do you make sure that HTTP requests from your app belong to a logged-in user? And how do you find out if that user is subscribed to any payment plan? Or get any metadata associated with that user? Easy! Simply forward the requests cookie header to and see the response.

on this page: