Skip to content

About

An independent software company.

Elyonox Technologies builds products it operates and software for businesses that need something more specific than an off-the-shelf tool.

We build two things: products we operate, and systems shaped around one team's workflow.

Elyonox is a software company with two connected parts: products we own and operate, and client engagements where we design and build a system around a specific operation. Product work keeps us close to production. Client work keeps us close to operational problems. Across both, the work spans applications, AI systems, fintech, agriculture, and the APIs that connect them.

Products and client work.

Two kinds of work, held to the same standard.

Products we operate

Mesob is our public product. We operate a broader portfolio of products and platforms that are not listed here. Across the portfolio, we maintain what ships, release changes, and live with the architecture decisions.

Client systems

Client projects start with a specific operation: map the workflow, define the system, ship the smallest useful release, and support it after launch.

How we work

How a project moves.

Each stage produces something you can review: a defined problem, an agreed scope, a working release, and a supported handover.

Understand the work

We start with the workflow, the people, and the constraints. You get a written understanding of the problem before scope or design is proposed.

Define the system

We define the data, roles, edge cases, and smallest useful release. You approve the scope before build starts.

Build in the open

We work in short increments and share working software as it takes shape. Decisions are made against the product, not a document.

Stay available

We hand over a documented system and stay available for fixes, maintenance, and improvements. Support terms are agreed before launch.

Principles

What we optimize for.

Start with the workflow

We look at how work moves between people before deciding what the interface should do.

Publish what we can verify

Products in development are labelled as such. Client work is published when the client approves the details.

Build for operation

A working screen is only part of the job. Permissions, failure states, documentation, and maintenance matter too.

Start a conversation

Tell us what you need built.

Describe the workflow, the constraints, and what is not working. We will tell you whether we are the right fit.