Platform
The whole loop, in one tenant.
Nihub is a multi-tenant sprint planning and delivery operations platform. This page is what it runs today, followed by what it does not run yet. Both lists matter when you are deciding.
Backlog
Refinement that survives contactDependencies, readiness, bulk operations, and issue collaboration with quarantined attachments and clean-only download.
Capacity
Deterministic planning inputTeam capacity, skill demand, and pairwise workload identity, so the plan is built against people rather than optimism.
Sprint
An atomic startThe sprint starts once. The baseline freezes the workflow version, and later workflow publications do not rewrite history.
Execution
Governed scope changeWorkload-aware work in progress, legal transitions only, and admission control that is observable instead of silent.
Risk
Signals with ownersEvidence-bearing signals, a decision rationale that is required rather than optional, and interventions with a name and a date.
Retrospective
Learning that is linkedAnonymous policy, grouping and discussion, exact risk and evidence links, action transitions, and unresolved prior actions kept in view.
01 · The chain
Customer truth and delivery truth are the same truth.
The commercial workspace is not a separate product bolted to a board. It shares the tenant, the authorization model and the audit trail with planning.
Commercial operations
- Leads and atomic conversion. One transaction produces the Account, the Contact and the Opportunity, or produces nothing at all.
- Proposals, contracts, renewals. Immutable revisions, acceptance snapshots, acceptance-derived contracts, and renewal lifecycles that carry their rationale.
- Delivery evidence. An Opportunity leads to a Commitment leads to work you can actually inspect, behind account-ancestry authorization.
Client communication
- Versioned client-safe drafts. Internal detail is removed before anything is publishable, not after somebody notices.
- Immutable editions. A publication cannot be quietly rewritten after the client has read it, and the history stays.
- Assigned-client portal. Clients read only what is assigned to them, and acknowledgements are idempotent.
02 · Portfolio
Compare without committing.
Portfolio decisions are where over-commitment starts. Nihub makes the alternatives explicit and keeps the decision reversible until somebody chooses.
Programs and dependencies
Programs are first class. Dependencies between programs in the same portfolio are governed, reviewed, and keep the rationale for approve, hold or cancel.
Versioned scenarios
Scenario overlays are versioned and compared deterministically without activating anything. The comparison is a contract, not a rendered opinion.
03 · Integration
A machine identity is still an identity.
Integrations get the same treatment as people: a scope, an expiry, a containment path, and an audit trail.
Scoped service accounts
- Project and account scoped. A machine reaches exactly what it was bound to and nothing adjacent.
- Expiring credentials. Rotation and targeted revocation are ordinary operations, not incident response.
- Consequential actions refused. A service account may read and draft a Proposal. It may not accept terms.
Signed webhooks
- Project-scoped subscriptions. A subscription cannot widen itself into the rest of the tenant.
- Durable delivery attempts. Attempts are recorded, retried within bounds, and dead-lettered rather than lost.
- Terminal replay lineage. A replay says what it replayed and stays attached to the original.
04 · The boundary
What is not built yet.
A platform that will not tell you its gaps is asking you to find them in production. These are open.
Not shipped
- Contract amendments, qualified e-signature and document rendering.
- Service desk, billing and payments, and the finance module around them.
- Broader real-time collaboration and the versioned automation builder.
- Connector marketplaces, analytics, and external intelligence providers.
How to read that
Nihub is a tested product foundation with a complete planning loop, a governed commercial workspace, and a deployment pipeline that refuses to promote an image it cannot verify. It is not a finished suite, and it does not claim to be one.
If a capability matters to your decision and it is on the left of this section, treat it as unavailable today.
Get in
Open it, or read how it refuses.
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.