SayHex Platform
The canonical overview of how SayHex works
SayHex is a governed AI platform for licensed teams that need reviewed access, department-scoped work, protected portal channels, and customer-edge or managed-cloud rollout planning.
Canonical product overview
The Platform page is the source for public SayHex product understanding
Use this overview to understand the product before moving into features, departments, deployment, licensing, security, or a reviewed demo request.
Product model
SayHex connects signed licensing, project scope, department access, SCU capacity planning, and customer review into one governed adoption path.
Public surfaces
Buyers can compare the public website, protected User Portal, login-only Customer Admin, API planning, Telegram channel planning, and demo request path.
Rollout choices
Teams can plan customer-edge hardware appliance or SayHex Managed Cloud deployment choices without receiving public setup details or private rollout instructions.
Planning focus
What buyers can plan on this page
Use this page as the public product overview for what SayHex is, who it serves, how access is reviewed, which channels are available, and where the current maturity boundary stands.
What SayHex is
A governed AI platform for organizations that want assisted work to stay inside signed license scope, project ownership, approved channels, and reviewable customer controls.
Who it serves
Business, support, operations, technical, creative, regulated, and administrative teams can compare department scope before protected access is provisioned.
How access starts
Public visitors request a reviewed demo or use protected portal login paths. Customer Admin access remains login-only after SayHex approval and provisioning.
How work is organized
SayHex organizes 312 catalog capabilities across 18 Platform departments so buyers can plan scope, channels, SCU capacity, and responsible review before rollout.
Where it can run
Deployment planning can compare customer hardware appliance and SayHex Managed Cloud options without exposing host details, private setup steps, or public self-service environment changes.
Current readiness boundary
The public website describes the catalog and reviewed access path while department operation remains bound to current maturity evidence and fail-closed behavior.
Claim boundary
Public product claims stay tied to signed licensing, approved channels, current maturity evidence, and reviewed rollout decisions before any customer-facing department work begins.
Every public promise stays tied to reviewed access, approved channels, and the current maturity evidence.
Launch FAQ
Questions buyers ask before requesting SayHex review
These answers address launch-critical objections without turning the public website into account setup, pricing approval, protected product access, payment, or production-readiness proof.
Is SayHex production-ready today?
The public website reflects the current maturity evidence: 312 catalog capabilities, 0 implemented, 3 runtime-tested, and 0 production-ready. Live use stays behind reviewed rollout evidence and fail-closed access until that evidence changes.
Can a visitor create Customer Admin access from the website?
No. Customer Admin access is login-only at https://portal.sayhex.com/admin after SayHex review, approval, and provisioning. The public request-demo form starts review; it does not create Customer Admin access.
What happens when an end user self-registers?
End User Portal self-registration creates a pending access request only. Department execution, API clients, Telegram actions, connectors, workflows, and SCU usage remain unavailable until Customer Admin approval and provisioning are complete.
Are public prices or commercial terms final?
No. Public pricing content helps teams prepare scope, rollout, support, and access questions. Final values, billing arrangements, legal wording, license scope, and account access decisions require approved SayHex review.
Can buyers choose how SayHex is deployed?
Buyers can compare customer-edge appliance and SayHex Managed Cloud planning paths before rollout. The website explains ownership and support expectations, but it does not publish setup steps, deployment access, or environment changes.
What should visitors avoid sending through public forms?
Use contact and request-demo forms for business context, rollout goals, and safe planning questions. Do not submit passwords, secrets, protected account data, diagnostic files, customer records, payment details, or confidential operational exports through public website forms.
Department inventory
18 platform departments can be compared before customer delivery begins
The catalog helps teams compare department scope, access channels, and readiness while customer delivery stays behind reviewed maturity evidence.
- SayHex 3D: 12 contract-defined capabilities
- SayHex Agent: 8 contract-defined capabilities
- SayHex Assistant: 7 contract-defined capabilities
- SayHex Business: 42 contract-defined capabilities
- SayHex Coder: 23 contract-defined capabilities
- SayHex Detector: 9 contract-defined capabilities
- SayHex Doc: 9 contract-defined capabilities
- SayHex Doctor: 14 contract-defined capabilities
- SayHex Financial: 9 contract-defined capabilities
- SayHex Food: 21 contract-defined capabilities
- SayHex Law: 11 contract-defined capabilities
- SayHex Live: 20 contract-defined capabilities
- SayHex Security: 15 contract-defined capabilities
- SayHex Smart: 19 contract-defined capabilities
- SayHex Studio: 18 contract-defined capabilities
- SayHex Support: 31 contract-defined capabilities
- SayHex Talent: 8 contract-defined capabilities
- SayHex Teacher: 36 contract-defined capabilities
Rollout planning
Start with the canonical Platform overview, then move into features, departments, deployment, licensing, or a reviewed demo conversation.
Use this route to prepare the next commercial or technical conversation, then continue through reviewed demos, licensing, and provisioning rather than public self-service.