ForjioHuudisIdentityPlugipayPaymentsStorlaunchE-commerceFulkrumaFulfilmentRiplloMarketingLinkSnapShort URLsPawpadoGPU streamingCatentioAgent runtime
Huudis Docs
⌘K

Introduction

Huudis is the identity provider for the Forjio family — a set of independent SaaS products (Plugipay, Storlaunch, Fulkruma, Ripllo, LinkSnap, Pawpado, Catentio) that share one login. If you've used any of those products, you already have a Huudis account.

Huudis handles the boring, hard parts of identity so the Forjio products don't have to: email/password sign-up, social sign-in (Google, Apple, Facebook), MFA, password reset, OIDC for portal apps, device flow for CLIs, refresh-token rotation, and an admin API for managing OIDC clients, workspaces, end users, and IAM policies.

New to Huudis? Start with the Quickstart — you'll register an OIDC client and sign a real user in within ten minutes.

What's here

The docs are organized the way you'll use the product over time:

  • Getting started — sign up for a workspace, install an SDK, sign your first user in.
  • Core concepts — the model behind accounts, workspaces, users, OIDC clients, identity providers, sessions, and MFA factors.
  • Authentication — how OIDC works at Huudis, social providers, password reset.
  • Portal — a tour of the Huudis dashboard at huudis.com.
  • API reference — the public REST API and how to authenticate against it.
  • SDKs — per-language guides for @forjio/huudis-node, the huudis package on PyPI, and github.com/hachimi-cat/huudis-go.

How Huudis fits in the Forjio family

Every Forjio product points its OIDC client at the same Huudis instance. A user who signs up on Storlaunch can later open Plugipay and skip the password screen entirely — the Huudis session is already valid.

Huudis owns:

  • Passwords, password resets, MFA enrolment.
  • Sessions and refresh tokens.
  • The list of OIDC clients allowed to talk to it.
  • The list of identity providers (Google, Apple, Facebook) wired up.

Huudis does not own anything product-specific: payment customers belong to Plugipay, storefronts belong to Storlaunch, GPU instances belong to Pawpado. Huudis only knows that a particular huudisUserId exists — what they do with it is up to each product.

If you only need to integrate against Huudis as a relying party (i.e., let your users sign in with their Huudis identity), you don't need to read this entire site — start with OIDC overview and then SDK overview.

Reach us

Ready? Go to the Quickstart.