Information

Payments, access, and public workflow rules

A factual page for billing basics, access levels, and how public tools connect to the registered product experience.

What teams usually ask first

What works without registration
When paid access becomes relevant
How public tools map into the main workspace
Access

Public pages answer before they require trust

Home, pricing, information, help, and public tool pages remain indexable and usable as an external-facing product layer. Registration becomes relevant when the team needs continuity, history, and shared context.

Billing

Pricing should feel operational, not abstract

The billing surface explains what is free, what scales with credits, and when a team should move from occasional checks to steady monitoring.

  • Entry via public tools and pricing
  • Clear differentiation between guest, free, and pro value
  • No ambiguous upgrade language
Product flow

Public tools are the first conversation, not the whole product

The goal is to let a visitor answer one concrete question fast, then show how the main workspace connects projects, history, AI visibility, and billing in one place.

FAQ