Skip to content

Investors

Institutional position

An engineering institution, built on a long horizon.

Ordfall is building an institution of software engineering and cybersecurity for critical systems — systems whose failure has consequences beyond the screen. The company is private and under construction. This page holds what exists today: the letter stating why it exists, the principles under which it agrees to work, and the documents anyone can read before speaking to us.

Identification

Stage
Under construction
Location
Brazil
Nature
Private company. Not publicly listed.
Legal identity
Pending publication

Institutional position

Position

01

What is being built

One discipline

Software engineering and cybersecurity are treated here as a single discipline, because in operation they already are one: how well a system was built is what decides how it behaves under attack, under load, and after the person who understood it whole has left. Ordfall was assembled to work on both at once, rather than delivering them as two reports that reach the same committee months apart and in incompatible vocabularies.

02

Why a long horizon

What is built well is only judged later

Declared boundaries, known dependencies, observable state, recorded decisions and a recovery path someone has already walked before needing it: none of those properties is sophisticated, and every one of them is expensive to add afterwards. A company that wants to be judged on them needs time, because the work shows on the day the system is genuinely tested — not in the week it was delivered.

03

What can be examined today

Judgement, before track record

There are no results to report, no clients to name and no metrics to display, and we are not going to invent any of the three to look more established than we are. What exists to be examined now is judgement: what Ordfall publishes, what it refuses to treat as a formality, and the conditions it imposes on itself before touching any environment.

Founding document

Ordfall's Founding Letter

Why we exist, what we refuse to treat as a formality, and what we want to still be standing ten years from now.

The letter states why the company exists and what it refuses. It is where any assessment of Ordfall should begin.

Published
Reading
4 min

Record

Institutional publications

Letters and company statements, in the order they were published.

  • Statement

    Ordfall opens private briefings for organizations

    A direct channel for organizations to describe their technical context. No sales form, no contact cadence, no automatic subscription to anything.

  • Statement

    Ordfall publishes its founding letter

    The letter states why the company exists, what it refuses to do, and the conditions under which it accepts work. It is published in full, with no gate.

  • Statement

    Introducing Ordfall

    A software engineering and cybersecurity company for systems whose failure has consequences. This site is its first public surface.

  • Letter

    Building an Institution for Systems That Cannot Fail

    The founding letter says why we exist. This one says what we are building: judgement that accumulates, refusal as part of the work, and a measure that can only be read in years.

Governance

How Ordfall agrees to work

These are rules of operation, not corporate instruments: Ordfall publishes no board, no committee and no by-laws, and these principles describe none of the three. They hold for every engagement, from the first assessment to delivery.

01

Authorisation before execution

Rule

Nothing is run against an environment before scope and written authorisation from someone with the standing to grant them.

What it costs

An urgent request without authorisation waits. The hurry belongs to the incident, not to the people called in to contain it.

02

Least privilege

Rule

The access granted is the smallest that allows the contracted work to be done, for as long as the work lasts.

What it costs

Access is named and temporary, and is handed back at delivery — not at the end of the contract, and not when someone remembers.

03

Evidence discipline

Rule

Every technical claim Ordfall makes has recorded, dated evidence behind it that someone else can reproduce.

What it costs

A finding without evidence does not enter a report, even when it is almost certainly true and even when it would strengthen the argument.

04

Independence of the recommendation

Rule

The technical recommendation does not depend on what Ordfall earns from it.

What it costs

When the correct decision is to commission no further work, that is what the report says — written with the same care as any other recommendation.

05

Continuity

Rule

Work is delivered so that another team can operate it without Ordfall.

What it costs

Documentation, recorded decisions and a reversal path are part of the delivery, not an extra billed afterwards.

Correspondence

It is Ordfall's only commercial address. We read and reply in Portuguese and in English, from Brazil.

This page carries no results, no clients, no metrics and no projections, because Ordfall has none of them to report.