Request a technical demonstration
Walk through the governed lifecycle in the local demonstration stack: intent, admission, permit, mediation, observation and evidence, including refusal and unknown outcomes.
Contact
Bring the hard question.
A technical demonstration, a design-partner evaluation, an architecture review or an integration discussion. All of them start with the constraint, the action boundary and the evidence you need.
Engagement paths
Choose the conversation that fits.
Each path below leads to the request form or to a page that explains the programme. The form records the specific request type while using one of the two intake kinds the route accepts.
Become a design partner
Work through a bounded adoption path with one control problem, defined fixtures and an explicit statement of what the evaluation did and did not verify.
Request an architecture review
Discuss where an independent admission and mediation boundary would sit in your system, which actions would be registered, and where bypass paths remain.
Discuss an integration
Talk through connectors, execution adapters and read-back. Integration scopes are defined under engagement; no connector certification is claimed.
Contact the team
General enquiries, research correspondence or a question that does not fit the categories above. Technical detail in the first message saves a round trip.
Email the team
Prefer direct email? Describe the system boundary, the action you are trying to govern and the invariant or obligation that matters. Do not send secrets or production personal data.
Send a request
Route the enquiry to the right conversation.
Choose the request type and describe the system boundary, action or invariant you are evaluating. The form posts only the fields you enter to a same-origin route. If no intake receiver is configured, the site says so and nothing is stored or forwarded.
Prefer email? Write to contact@nigenje.com. No pricing, service-level commitment or support agreement is implied by sending a request.
What to expect
A person reads the technical detail.
Enquiries are handled by the engineering side of NiGeNje. Expect a reply to the email you provide, not an automated sales sequence.
- We read the boundary, action class and invariant you describe.
- We tell you where the current implementation stops, including bypass paths.
- If there is no fit today, we say so rather than keeping an enquiry open.
- No marketing sequence or third-party lead distribution is configured.
Questions
Before you write.
What should the first message contain?
The system boundary, the action or workflow you want governed, the invariant or obligation that matters, and the failure modes you need represented. A short, concrete description moves the conversation further than a broad request for information.
Is the form connected to a receiving service?
Not yet. The form posts to a same-origin route that validates the request and then reports that no confirmed intake receiver is configured. Nothing is stored or forwarded in that state. Email is the reliable fallback while intake is being configured.
Are pricing, SLAs or support terms available?
No pricing, service-level agreement, support commitment or deployment guarantee is published or implied. Commercial terms, if any, would be discussed separately after the technical scope is understood.
Can I request a security questionnaire response?
The public security page already states what is enforced, what is partial and what is not claimed. A more detailed review can be discussed under engagement, but no certification, audit report or compliance attestation exists to send.
Where are you based?
NiGeNje is based in Nairobi, Kenya. Engagement is remote by default, and the technical work is bounded to a defined evaluation scope rather than an on-site deployment commitment.
Or start with the boundary
Read what is enforced before you evaluate it.
The security page states the explicit NARG limitation and what NiGeNje does not claim. It is the fastest way to decide whether an evaluation is worth your time.