FAQ

Frequently asked questions for cautious buyers.

Short answers for the product website, deployment model, pricing placeholders, support boundaries, and future portal expectations.

Static answers No legal advice No support tickets No appliance control

FAQ

Answers that keep the public website boundary clear.

These answers are static product education and do not create accounts, support tickets, or appliance actions.

No. BlackBox Node is positioned as a private appliance that brings local model execution and local retrieval into the client environment.

No. This website is static product information and should not receive confidential client, patient, case, investigation, student, or regulated data.

No. Appliance administration belongs inside the private BlackBoxNode.Web appliance UI in a client environment, not on this public website.

No. Customer portal and account management are coming later and require a future authenticated design.

No. Support ticketing is coming later. Phase 9 keeps support routing static and non-functional until an authenticated support design exists.

No. Pricing rows use placeholders until commercial approval, deployment discovery, and contract terms are agreed.

Sensitive files, logs, secrets, incident evidence, and regulated data should use approved secure channels agreed during onboarding, not the public website.

BlackBox Node is positioned around client-controlled local deployment. Final contractual data ownership and handling terms must be agreed during deployment planning.

Boundary

Static answers only.

This public website provides product information and support routing only. Do not submit confidential client, patient, case, investigation, student, regulated, or commercially sensitive data through this public website.

Next step

Discuss a private intelligence deployment.

Use the contact path to talk through data sensitivity, sector obligations, appliance shape, and rollout readiness before implementation decisions.