Services

A technical partner for companies that need things to work.

Noryx works with small and mid-sized companies on concrete problems: software to build, infrastructure to straighten out, a website to redo, a technical decision to make. Held to the same standard as its own products.

A

Software

Covers

  • Web applications
  • Business applications
  • APIs and integrations
  • Automation
The problem
A spreadsheet doing a software’s job. An off-the-shelf tool that fights the way you work. A task someone repeats by hand every week.
The approach
Start from the actual work, not a feature list. Build the application or API on proven technology, with tests wherever a mistake would be expensive.
What you get
A tool that does one precise job and does it right — and stays readable for whoever picks it up next.
B

Infrastructure

Covers

  • Linux
  • Virtualisation (Proxmox VE)
  • Containers and continuous deployment
  • Servers and cloud
  • Monitoring and backups
The problem
A server set up long ago that nobody dares touch anymore. Releases done by hand. No alert when something goes down.
The approach
Describe the infrastructure instead of patching it: containers, versioned configuration, repeatable deployments, tested backups and monitoring.
What you get
Systems you can rebuild, update without dread, and whose state you know at any moment.
C

Digital products

Covers

  • Websites
  • Interfaces and design systems
  • Prototypes
  • Internal tools
The problem
A website that doesn’t say clearly what you do. An interface your team works around. An idea you’d like to test before putting money into it.
The approach
Treat design and code as one job. Write the content first, build pages that are fast and accessible, prototype quickly while the question is still open.
What you get
A site or interface that loads fast, reads well on a phone, and says exactly what it needs to.
D

Technical consulting

Covers

  • Architecture
  • Code and infrastructure audits
  • Technical guidance
  • Choosing tools
The problem
A technical decision with nobody to challenge it. A vendor whose work you can’t assess. An existing system whose real state nobody knows.
The approach
Read the code, the infrastructure and the documentation, ask the right questions, then write down what was found — plainly, without drama.
What you get
A written assessment, recommendations ranked by priority, and someone to ask the next question.

Who it’s for

  • Small businesses

    No in-house tech team, and a need for one person who understands the whole picture — from the domain name to the application.

  • Mid-sized companies

    A team in place that needs reinforcement on something specific: infrastructure, an internal tool, an audit before a decision.

  • Founders and independents

    An idea worth testing properly, with a prototype that can grow into a real product if the test works out.

How Noryx works

  1. 01

    Understand

    The problem before the solution. Who uses what, what gets in the way, what actually matters.

  2. 02

    Design

    A clear, written solution with its scope and its limits. Agreed on before the first line of code.

  3. 03

    Build

    Short, visible steps. Readable code, tested where it matters.

  4. 04

    Ship

    Tooled deployment, documentation, handover. Nothing that only lives in someone’s head.

  5. 05

    Improve

    See what actually gets used, fix, refine. Useful software is never quite finished.

Getting started

Describe the project or the problem in a few lines. The reply suggests a call to pin down what you need, followed by a written proposal: scope, steps, and what’s out of scope.

Describe your project