M1Method

From a written specification to a running service

Valeron carries software through five stages, from the written specification to day-to-day operations. Its own products go through the same stages, and they are held to the same engineering practices as the systems delivered to clients.

Follow the stages

Illustrative

  1. 01Specification
  2. 02Data model
  3. 03Service
  4. 04Deployment
  5. 05Operations

01Stages

Five stages, one line of work

Each stage settles something that the next stage depends on. The work moves in one direction: from what is written down to what is running.

  1. 01

    Specification

    Work starts from a written specification. It states what the system does, and within which limits. Later decisions are checked against it.

    SettlesWhat the system does, and within which limits

  2. 02

    Data model

    The data model is settled first. Entities, their relations, and the rules that keep the data consistent are decided before the code that depends on them. Services, interfaces, and reports are built on it.

    SettlesThe shape of the data, and its rules

  3. 03

    Service

    The rules of the system go into code. For a backend, that means services and APIs in .NET and C#. For a trading system, it means expert advisors in MQL4 or MQL5 that carry strategy logic, risk controls, and order execution. Web interfaces are built to operate them.

    SettlesWhat the system does when it runs

  4. 04

    Deployment

    The system leaves the repository and becomes a running service. Deployment belongs to the same work, from the data model through to deployment, and is not a separate hand-over at the end.

    SettlesWhere and how the system runs

  5. 05

    Operations

    A running SaaS product needs authentication, billing, background processing, and day-to-day operations. These are the parts that are easy to underestimate, so they are planned from the specification onward and not added at the end.

    SettlesHow the system keeps running

Valeron takes software products from a written specification to a running, multi-tenant service. That includes the parts that are easy to underestimate: authentication, billing, background processing, and day-to-day operations.

02Practice

One standard for client systems and its own products

Valeron builds and operates its own software products alongside client work. That work is funded and directed internally, and it is held to the same engineering practices as the systems delivered to clients.

Delivered to clients

Client systems

Trading automation for MetaTrader 4 and MetaTrader 5, backend services and APIs in .NET and C#, and software products taken to a running, multi-tenant service.

  • Trading systems
  • .NET backends
  • SaaS products

Funded and directed internally

Its own products

Software that Valeron builds and operates itself. OnLooq, its web analytics, runs on valeronit.com.

  • OnLooq

The same engineering practices

03Scope

The same stages in all three services

The stages do not change between an expert advisor, a .NET backend, and a multi-tenant SaaS product. What changes is what each stage contains.

Service 01

Algorithmic trading systems

Expert advisors for MetaTrader 4 and MetaTrader 5, covering strategy logic, risk controls, and order execution.

Service 03

SaaS product engineering

Software products taken from a written specification to a running, multi-tenant service.

04Contact

Send a message to Valeron

The contact form is the only contact channel. Valeron replies to the address given in the form.