Live planning service
Opening the delivery room…
Checking your session and current sprint.
Live planning service
Checking your session and current sprint.
Nihub joins customer operations and delivery operations in one multi-tenant system. Leads, opportunities, commitments, portfolio, sprints, release evidence and the status your client reads all sit on one chain, and every link is inspectable.
Governed sprint intelligence ships disabled. No external model provider is enabled and no outbound data path exists.
System index
Intelligence, default state
DisabledTurn it on and you get deterministic, evidence-linked recommendations that still cannot apply themselves. A human who is not the proposer has to approve, and the application stays reversible.
No external provider. No outbound data path. Immutable receipts on every decision, including the refusals.
Isolation
Row-level security in the databaseTenant separation is enforced by PostgreSQL, not by remembering to add a clause to a query.
Authorization
Deny by defaultRole and relationship checks refuse anything they have not been explicitly told to allow.
Evidence
Append-only auditConsequential actions leave a record with actor, target, result and correlation, and it is not edited afterwards.
Commands
Exact idempotent replayA replayed command returns its first result instead of doing the work twice.
Constraint
Capacity is not a suggestionPlanning is workload-aware, so a sprint cannot quietly exceed the people who have to deliver it.
Presentation
WCAG 2.2 AA is the targetFour themes, full keyboard operation, and a locale, time-zone and number policy the tenant sets.
01 · What it is
Most teams run the customer half and the delivery half as separate tools and reconcile them by hand. Nihub keeps both in one tenant so the reconciliation is not a job anybody has to do.
Commercial truth lives beside delivery instead of in a tool the delivery team cannot read.
Planning that knows what the work protects, and refuses to pretend about capacity.
02 · The gate
Most delivery tools are adding a model that changes your plan and tells you afterwards. Nihub puts a boundary in front of that and makes the boundary the product.
Proposed
A bounded recommendation is derived from the sprint. Same input, same output, with a link to every piece of evidence it used.
Held
The change waits at an approval boundary. A stale recommendation is denied rather than quietly reapplied to a plan that moved.
Applied
Someone other than the proposer approves. The application is reversible and the receipt survives the reversal.
This ships disabled. There is no external intelligence provider and no outbound data path, and the executor and retention roles are isolated from each other.
03 · The trace
Operate it. Pick a commitment, advance the chain, and watch what happens when a governed recommendation meets the approval boundary. Keyboard works throughout.
The Opportunity becomes a delivery commitment with a date and an owner that the delivery side can actually read.
The console opens with the first three links already traced. Advance it, or pick any stage to read its evidence.
Drawn in this page from fixed demonstration data. The three accounts are invented for this console. Nothing here reads a tenant, calls a network or resembles a screenshot of the product. It exists so the two rules underneath the trace are operable rather than described.
04 · Tenancy
Multi-tenancy is treated as a product feature with tests behind it, not as a deployment detail somebody will harden later.
05 · Reach
WCAG 2.2 AA is the target for supported workflows. Presentation is a tenant policy with personal overrides, so the way dates, numbers, language and colour appear never changes what anyone is allowed to do.
Get in
Nihub is built to be audited before it is admired. Start with the workspace or start with the boundary. Both doors are on this page.