Strong commitment to projects of any size.
From multinationals to rising startups and SMEs, the commitment does not scale down: the same review, the same documentation, the same accountability. We build it for ourselves first, then for clients.
See the business unitsBracketmore
Software for decisions that are hard to reverse.
Bracketmore is a technology company that builds its own software as well as yours. Deal Accelerator and MedIAudit are its products, running in regulated environments. BeyondNoCode is its services unit, working on client systems. OpenBracket is what it publishes opensource.
How Bracketmore works
The same standard at every size.
Commitment at any size.
A small build gets the same review, the same documentation and the same accountability as a large one.
Teams shaped to the problem.
Regulated-data work, product builds and security work are staffed by different specialists. There is no single roster for everything.
Adaptable across contexts.
The work runs across countries, sectors and stacks. The method holds; the tools change with the problem.
Behaviour before technology.
We start from how people use the system and what the operation needs, not from a feature list.
Business units
Three products, one services unit, one engineering standard.
-
Deal Accelerator
Product · Deployed inside the acquirer’s perimeter
Due diligence for pharmaceutical M&A. Runs inside the acquirer’s own infrastructure. No data leaves the environment, including to us.
Find out more -
MedIAudit
Product · Regulated health data · Brazil
Medical claims audit for Brazilian health operators. Patient data resident in Brazil, under ANS, CFM and LGPD.
Find out more -
BeyondNoCode
Services unit · Client systems
Custom software and cybersecurity for client systems. Practical, build-focused, and set up to hand the work over. Agency and build enquiries go here.
Find out more -
OpenBracket
Open source · Permissive licences
What we publish, with the commit history intact. The parts of our work that can be read before anyone signs anything.
Find out more
Footprint
Where the work is.
Ten project locations on five continents. Teams are shaped to the problem, not to a city.
Evidence
What can be checked.
Products in regulated production
Deal Accelerator runs inside acquirers’ own networks. MedIAudit holds patient data under ANS, CFM and LGPD.
Long-term client relationships
Client relationships run for around four years on average. Several of the engagements on the map are in their third year or later.
Ten project locations, five continents
Client work in Australia, the United States, Brazil, Europe and the Gulf, listed on the map above.
Security before release
In-perimeter deployment, data residency and review before ship. The security posture is published on its own page, and the detail under NDA.
Signals
What we’re exploring.
Software changes faster than the reasons for building it. These are the ideas we’re testing, mostly on our own products first.
-
Mobile-first and API-first shaped a decade of product decisions: design for the smallest screen, expose everything as a service. Both assumed a person at a screen or a developer at a keyboard.
We’re watching what happens to those disciplines when the consumer of a system is an agent rather than either.
Status · watching
-
MCP-first is the idea that a system’s capabilities are described well enough that models and agents can use them without a bespoke integration.
It is early and unsettled. We’re exploring it on our own products before recommending it to anyone, and paying attention to what it means for regulated data.
Status · exploring
-
A feature list describes what a system could do. Observed behaviour describes what people actually do with it, and where the operation gets stuck.
We’re thinking about products that start from the second. It changes what gets built first and what gets measured afterwards.
Status · thinking about
-
Products can adapt to how they are used. The open question is how far that should go, and where it has to stop when the data is regulated.
We’re testing this in narrow places first: defaults, ordering, and the questions a system asks, rather than the decisions it makes.
Status · testing
The mark
The bracket is the perimeter.
Every Bracketmore product is drawn inside a bracket. The bracket is what we build around your data: a boundary that holds. Protection, privacy, and sovereignty over what is inside it. The glyph inside says what the product does.
- BracketmoreTwo triangles converging. Separate teams, one standard.
- Deal AcceleratorValue added to both companies, inside one perimeter.
- MedIAuditThe audit decision, recorded and simplified.
- BeyondNoCodeOne triangle. The half that builds, pointed at your work.
- OpenBracketThe only mark that does not close. Nothing inside it is held back.
Partners and clients
In their words.
OpenBracket
You can read our code before you sign anything.
Deal Accelerator runs inside your own infrastructure. MedIAudit holds patient data under LGPD. Neither is software you can trial on a laptop before committing to it, and a services engagement is a larger commitment still.
OpenBracket is how you judge the engineering anyway. The parts of our work that can be published, are, under permissive licences with the commit history intact. No NDA, no sales call, no account.
OpenFML is our financial modelling language. It is open source and unencumbered: models written in it stay yours and stay readable whether or not you stay a client.
// runway.fml: eighteen-month check on one operating planmodel runway { unit currency = BRL unit period = month input cash_start = 4_200_000 input burn_monthly = 310_000 input revenue_first = 96_000 input growth_monthly = 0.07 series revenue[m] = revenue_first * (1 + growth_monthly) ^ (m - 1) series net[m] = revenue[m] - burn_monthly series cash[m] = cash_start + sum(net[1..m]) assert cash[18] > 0 report breakeven = first m where net[m] >= 0}