Skip to content

SignalForge · Onboarding

From a request to a running environment.

Every screen below is real, on seeded data: this site, our admin app and your customer portal, with who does what at each step.

  1. You, on kajilabs.ai

    Request access

    A few details about your team and what you would use SignalForge for.

    The SignalForge access-request form on kajilabs.ai with name, work e-mail, company, role, the current data stack and a sentence about the intended use filled in
  2. Kaji Labs, in the admin app

    We review the request

    Requests are reviewed by a person, in order, against what we can onboard well.

    The admin SignalForge access-request queue listing applicants with company, status and dates, beside the registration-mode setting
  3. Kaji Labs, in the admin app

    Approve and invite

    Approval sends a personal, time-limited invitation that creates the account.

    One access request in the admin app: what the applicant told us, a Send invitation button, a status selector and an internal priority and tags panel never shown to the applicant
  4. You, in the customer portal

    Create the account

    The invitation link opens the portal; the account is yours from here.

    The SignalForge customer portal sign-up page, which creates an account from an invitation
  5. You, in the customer portal

    Choose a plan per environment

    Priced per environment, run by Kaji Labs; nothing is charged until you choose a paid plan.

    The portal's Add an environment page: Free, Pro and Enterprise tiers with their connector limits and monthly managed prices, then the managed hosting option listing what Kaji Labs provides
  6. Kaji Labs, in the admin app

    We provision and watch it

    Every environment reports in; the fleet view shows what went quiet.

    The admin Accounts page: every customer with their environments, instances online, licences expiring and billing issues, and a recent-activity list of instances reporting in
  7. You, in the customer portal

    Billing stays in the portal

    One card, entered once at Stripe's checkout; managed from the portal afterwards.

    The portal's Billing page showing this month's total before tax, the environments it covers and a Start a subscription button that leads to Stripe checkout

Where this is today

People first, then the portal.

Kaji Labs runs SignalForge for every customer. For now, a person does with you the steps the portal will automate next.

Today

  • A person reads your request and replies by e-mail, usually within two working days.
  • We set the environment up and send you its address and sign-in.
  • Billing is agreed with you directly. Nothing is charged until you choose a paid plan.

Next

  • A confirmation e-mail and a time-limited invitation link create your portal account.
  • You choose a plan per environment in the portal and watch it provision.
  • One card at Stripe's checkout; invoices and plan changes in the portal.

Ready to start?

Request access and we will review it and send an invitation.