Getting started using Omnistrate Web UI¶

To get started with Omnistrate Web UI, its really simple and you just need to follow quick self-onboarding steps:

Configure Cloud Accounts¶

To configure your own account, you can follow the steps described in Account Onboarding

Build SaaS Product¶

There are several options to start building your SaaS Product:

• Click "Hello world project" to build an example Mage AI service
• Click "Bring your container image" to build a service from your container image
• Click "Bring your Docker Compose" to build a service with your own Compose spec or one of our Certified templates.
• Reach out to [email protected] to build a service with Kubernetes Operators, Helm Charts, Terraform and more or follow our guides on how to onboarding with Omnistrate CTL.

Here is how it looks like:

Once you have submitted your service build, Omnistrate will build your service definition and deploy your SaaS Product in a Development environment

Launch SaaS Product¶

Once your SaaS Product has been created, you can optionally decide to make your SaaS Product live for any one to sign-up and access publicly.

Here is how it looks like:

If you click "Yes", Omnistrate will deploy your SaaS Product in a Production environment.

Getting started video¶

Hello world example using PostgreSQL¶

One of the easiest ways to get going is to leverage compose templates. You can existing templates or create your own. Here is a sample compose spec to create single writer Postgres SaaS:

version: '3.9'
services:
  postgres:
    image: postgres
    ports:
      - '5432:5432'
    environment:
      - SECURITY_CONTEXT_USER_ID=999
      - SECURITY_CONTEXT_GROUP_ID=999
      - POSTGRES_USER=username
      - POSTGRES_PASSWORD=password
      - PGDATA=/var/lib/postgresql/data/dbdata
    volumes:
      - ./data:/var/lib/postgresql/data

In the above case:

• We are using only 1 Resource (postgres) with the standard image (postgres) and infra (port: 5432)
• Given no account config is specified, the infrastructure for your SaaS is provisioned in the Omnistrate account
• There are a few static environment variables that will be injected into the runtime process like POSTGRES_USER

In general, the compose config allows you to specify:

• Resources and relationship across them
• Image(s)
• Environment
• Infrastructure
• Capabilities
• Account config information
• Enable/Disable Integrations
• SaaS experience (input/output params with constraints)

For detailed setup instructions, please visit here

Here is the generated Postgres SaaS from the above spec looks like: