n0hup@relay:~$ ./tailor --for your-environment

RELAY / RLY-01 · ENGINEERING

Tailored Solutions

Your infrastructure. Your workflow. A solution that fits.

Custom engineering for the work a generic tool cannot quite do: automate the repetitive task, connect the missing interface, make the operational picture clear.

[ DESCRIBE YOUR PROJECT ]View engineering services →

START WITH COMMUNITY EDITION

The RELAY AD Health Toolkit is available with source code, local reports and a synthetic demo. Use it as a starting point for agreed custom checks, reporting or evidence interpretation.

[ EXPLORE THE FREE TOOLKIT ]

01 / BUILT AROUND YOUR ENVIRONMENT

Adapt a small tool or commission a complete workflow. The starting point is your operating model, existing systems and the result your team needs.

IDENTITY OPERATIONS
AD and Entra inventory, group and permissions reports, GPO analysis and scoped joiner/mover/leaver automation.
MICROSOFT WORKFLOWS
M365 licence reporting, Exchange mailbox and mail-flow checks, Teams governance and client-specific integrations.
INFRASTRUCTURE TOOLING
Windows and Linux health checks, storage capacity reports, backup evidence collection and network configuration audits.
INTEGRATION / AUTOMATION
PowerShell, Python and Bash tools; API integrations; scheduled reports and operational dashboards.

These are examples of work that can be scoped, not an off-the-shelf product catalogue. Platform versions, API availability and permissions are checked during discovery.

02 / THREE WAYS TO BUILD

Adapt

Fit an existing client tool or script to a defined environment.

Deliverables: scoped modifications, configuration notes and agreed checks.

Build

Create a focused tool, report or automation for a repeatable task.

Deliverables: source code, configuration guidance, test evidence and an operator guide.

Integrate

Connect systems into a workflow with clear ownership and failure handling.

Deliverables: interface design, integration code, deployment and rollback instructions, and handover.

Custom quotation after discovery. Source delivery, usage rights, third-party dependencies, support and maintenance are agreed in the proposal.

03 / FROM REQUEST TO HANDOVER

  1. Describe the outcome

    Share the problem, environment, constraints and target date. Start with a short, non-confidential brief.

  2. Discover & scope

    Review dependencies, platform support and access needs. Agree deliverables, exclusions, acceptance tests, price and milestones before implementation.

  3. Prototype & review

    Validate the approach using sample or test data. Review the output together before expanding the implementation.

  4. Build & verify

    Implement the agreed scope, document configuration, test expected and failure paths, and record results.

  5. Deploy & hand over

    Use an approved change window and rollback plan. Deliver agreed source, documentation and knowledge transfer; confirm acceptance against the defined criteria.

  6. Maintain by agreement

    Choose whether to arrange ongoing support. Changes to scope, support coverage or platform compatibility are agreed separately.

04 / START A CONVERSATION

Describe the outcome you need. We will clarify scope, dependencies and deliverables before proposing the work.

Email: engage@n0hup.nl

This page prepares an email draft in your mail app. Nothing is sent until you send it there. No request data is stored by this page. Keep passwords, access tokens and confidential system details out of the initial message.