Hosted Components vs. Handler

​

Prefer hosted components

export const hexclaveClientApp = new HexclaveClientApp({
  tokenStore: "cookie", // or "nextjs-cookie" on Next.js
  urls: {
    default: {
      type: "hosted",
    },
  },
});

• Users land on Hexclave-hosted auth pages that stay up to date automatically.
• You do not need a /handler/[...] catch-all in your app for the default sign-in flow.
• Redirect helpers such as redirectToSignIn() send people to those hosted pages, then back to your app.

​

Own handler on your domain

1. Point urls.default at the handler component (this is also the SDK default if you omit urls.default):

urls: {
  default: {
    type: "handler-component",
  },
},

2. Mount the catch-all route your framework SDK documents — for Next.js:

import { HexclaveHandler } from "@hexclave/next";

export default function Handler() {
  return <HexclaveHandler fullPage />;
}

​

Mixing and custom pages

• Keep default: { type: "hosted" }, but set accountSettings: "/settings" (or { type: "custom", url: "/settings", version: 0 }) for a page you own.
• Keep most pages on the handler, but send signIn: { type: "hosted" } if you want only sign-in hosted.

​

Related

• Setup — framework setup, including the hosted urls default.
• Authentication overview — what the Authentication app covers.
• Local vs. Cloud Dashboard — development environment vs cloud project.