Think. Build. Secure. Leverage.

01 · Think

Innovation and discovery

We help your company shape the best solutions to its challenges and opportunities: discovery sessions, prototypes, and the evidence to choose what is worth building.

Start with a conversation

02 · Build

Development

Custom software and client systems, built by BNC, our development agency, with the same review, documentation and accountability as our own products.

BNC, our dev agency

03 · Secure

Security

Continuous pentesting and Red Team engagements by Bracketmore Security: a manual test, monitoring around the clock, findings within 24 hours.

Bracketmore Security

04 · Leverage

Products

Deal Accelerator for pharmaceutical M&A due diligence, MedIAudit for medical claims audit, and OpenFML, our open-source financial modelling language.

See the products

Footprint

Where the work is.

    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.

    • 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

    • 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

    • 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

    • Once agents read documents, call tools and act on behalf of people, the perimeter has to hold against inputs written to persuade rather than to break: prompt injection, exfiltration through tool calls, and identity for actors that are not human.

      We’re exploring it with Bracketmore Security on our own products first: what continuous pentesting looks like when the attack surface includes a model’s instructions.

      Status · exploring

    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.

    attack · perimeter · held
    Talk to us