Insites Docs Developers guide Get StartedCreating your first Application

AI answers drawn only from these docs, with links to the pages used.

Creating your first Application

Last updated on October 15, 2026.

The setup process of developing an application on Insites consists of the following steps:

  • Step 1: Sign up for an Insites Console account
  • Step 2: Create an Instance from the Console
  • Step 3: Create your codebase
  • Step 4: Setup the Insites CLI Tool
  • Step 5: Deploy to your instance

Step 1: Sign up for an Insites Console account

You need to sign up for an Insites Console account before you can build on Insites. To sign up for an account:

  1. Go to console.insites.io and click Create account.
  2. Set your email address and password.

You use the same Insites account for the Console, the Insites CLI and Insites CloudShell.

Congratulations! You can now begin building on Insites!

Step 2: Create an Instance from the Console

The Console is your central administration panel where you can create, manage, and configure your instances and applications built on Insites.

Note

Here are some important details about the Console:


  • The console allows you to created Instances which are either 'Staging' or 'Production' environments. When building your application you may have multiple staging instances for your development workflow, along with your production instance.
  • Each person in a Console account has one role: Viewer, Editor, Developer, Admin or Owner. Using the CLI and deploying need Developer or above. Admins and Owners manage people.

A summary of the steps needed to create an Instance on the Console is as follows:

  1. Go to Instances in the Console.
  2. Click Create instance.
  3. Follow the steps: name, type, source and pricing.
  4. Review your choices and create the instance.
Note

Please visit the documentation on Creating an Instance on the Console for more details.

Step 3: Create your codebase

Insites is framework agnostic and allows you to build your application in any frontend technology. Some common ones are VueJS, ReactJS and Angular. To correctly communicate with the Insites engine and API, your codebase should be organised into a specific directory structure. To create your codebase in a local environment, follow the Getting Started with the Insites CLI Tool guide.

What you’ll need:

  • Node.js
  • Insites CLI Tool

Step 4: Setup the Insites CLI Tool

The Insites CLI tool is a command line interface that helps you deploy configuration files and assets to your Insites application. It also allows you to use team collaboration tools like Git in your workflow.

You can use the Insites CLI to deploy or sync your codebase to the instance, as described in Getting Started with the Insites CLI Tool.

An overview of the steps needed to install the Insites CLI tool is as follows:

  1. Once you have Node.js installed in your machine, open your preferred command-line tool and run the following command:


  2. After installing the Insites CLI tool, run the following command to test if the tool was installed successfully:


    If everything went smoothly, it prints the version you installed (for example: 6.3.2).

Note

Please refer to our documentation on Getting Started with the Insites CLI Tool for more details on setting up and using the Insites CLI tool.

Step 5: Deploy to your instance

To create a project and deploy it to your Insites Instance, following these steps:

  1. Create an empty folder for your project.

  2. Navigate to the project's folder in the command line.

  3. Initialize the Insites directory structure.

  4. Create your environment.

    Your browser opens so you can sign in and approve. You can find the instance UUID in the Console, on the instance's CLI Commands tab.

  5. Upload your code to the Instance.

  6. Once your codebase is uploaded, you can use sync to automatically push your code to the instance when you save the file.

Have a suggestion for this page?

Didn't quite find what you are looking for or have feedback on how we can make the content better then we would love to hear from you. Please provide us feedback and we will get back to you shortly.