Appearance
SenHub Web
SenHub Web is the browser interface to the same project, configuration, build, device, and managed operation model used by SenCLI. The shared SenHub platform service and APIs—not the browser client—persist canonical state, enforce policy, schedule builds, create plans, and verify reported results.
Start by task
- Create a project and select its target.
- Select hardware, then configure modules and drivers.
- Trigger a build after validation passes.
- Provision a device and monitor synchronization.
- Add secrets and licenses only through the intended project and device workflows.
- Review module definitions, driver definitions, and configuration bundles before a build.
- Create a project when a team needs a separate release and Catalog selection.
The tasks above can also be performed through supported SenCLI command families. SenHub Web additionally emphasizes visual interaction plus tenant, account, team, plan, subscription, billing, and financial management. SenCLI additionally emphasizes terminal automation, structured output, CI, local tooling, and MCP.
For device operations, both clients can request the same intent and run a compatible local executor. The platform-generated plan, selected releases, artifacts, and reported facts remain the source of truth; the chosen interface does not change their semantics.
Project and access
- Project overview, project settings, and project templates explain the identity chain behind a build.
- Registration, authentication, API keys, and permissions cover access boundaries.
- Team members describes ownership and access review.
Build, configuration, and devices
- Review build artifacts, build status, and flashing before delivery.
- Use publishing configuration, configuration push, and configuration synchronization for immutable, auditable changes.
- For runtime state and protocol-aware actions, see device state and remote commands.
Hardware schema
- Pin capabilities, pin selection, adding drivers, and conditional fields explain how published component definitions drive validation.