/ About

Software does the work. People stand behind it.

OAKMONT (oakmonttechnologies.com) runs the routine operations small teams do not have staff for: automation, servers and web. Our platform executes at software speed and cost, and a real engineer verifies every result before it reaches you. This page is who does the verifying, and the standards they hold.

/ Founders

The people who own the outcome

OAKMONT is built and run by its founders, not outsourced to someone else.

Mateusz Jasiński, co-founder
Co-founder

Mateusz Jasiński

Wrote his first line of code at eleven and was paid for a project two years later. Twelve years of it since, with startups, enterprise clients and online platforms under real load. He works on the back end: architecture, the infrastructure under it, the automation that runs it, and the performance work that keeps it cheap to run.

David Nam, co-founder
Co-founder

David Nam

A finance graduate who worked in the industry before this. He co-founded OAKMONT to build something of his own, and spends his time on where an AI model belongs in how a business actually runs, and where it does not.

/ How work is made

AI-executed, human-verified

The same three steps sit behind every deliverable. It is a real sequence, not a slogan.

  1. 01

    AI drafts

    Our platform does the first pass on your request (the remediation, the fix, the report, the workflow) in minutes, not days.

  2. 02

    A person verifies

    A qualified reviewer checks the draft against the standard, corrects what is wrong and signs off. Nothing ships on the model's word alone.

  3. 03

    We deliver and stand behind it

    You get the finished work plus the record of who verified it. If it is wrong, that is on us to make right.

/ Who verifies

The people who sign off

Every result is reviewed by someone who does that discipline for a living, not a generalist rubber-stamp.

Accessibility specialists

WCAG 2.1 AA and Section 508 reviewers who check remediation by hand and against assistive tech, then issue the conformance record.

Systems engineers

The people who verify server work (patches, backups, incident fixes) and carry the pager when something breaks at 3am.

Editors and QA

Reviewers who read every generated document and report for accuracy and tone before it carries your name.

The reviewer of record

Each deliverable names the person who signed off. That accountability is captured in the job's provenance, not hidden.

/ How we operate

What we hold to

Data is the source of truth
The model is a product derived from verified work, versioned and retrainable. The record of what was delivered outranks any one model's output.
A human is always in the loop
Autonomy is earned per service and can always be dialed back. A customer can hold any service to review; we never remove the human check to save time.
We own the outcome
Fixed prices agreed up front, an SLA you can hold us to, and a rate locked for as long as you stay. If the work fails, the fee does too.
/ Trust

The paperwork to back it

The verification model is only as good as its evidence. Every deliverable is auditable, and the security posture is documented.

  • Full audit trail of every change
  • Per-deliverable provenance: draft, edits, reviewer
  • Role-based access, data isolated per organisation
  • Self-hostable when policy requires it

Work with a team that verifies its own output.

Start with a free health check, or tell us what you need and get a fixed price back.