Sign In

Customer access is not yet exposed through a public self-serve sign-in screen.

The sign-in button now lands on a real page that sets expectations, instead of pointing to a placeholder hash.

No dead endClear expectationSupport pathFuture-ready route

Current state

The repository does not yet expose an authenticated application shell for end users.

  • There is no public login form in the current build.
  • Marketing, docs, checkout, and operational routes are the active surfaces.
  • This route reserves a stable URL for future account access.

What users should do now

A placeholder sign-in link is misleading; this page is intended to be direct instead.

  • Use the contact page for account-access requests.
  • Review docs and pricing before asking for onboarding help.
  • Expect a future authenticated workspace once customer access ships.

Why keep the route

This is useful even before authentication exists.

  • Navigation no longer contains a broken anchor.
  • Visitors receive context rather than confusion.
  • The product can later swap in a real auth flow without changing the URL.