Company · Ax0s, LLC

2 operators, one accountable record.

AX0S is Chris Blaschke and Aaron Dyson. We build the product, run it on our own memory, and publish what holds and what does not. Nothing here is a team you meet later.

  • People on the record 2
  • Product ax0s-memory
  • Operating contact chris@ax0s.io
  • Public claims 39 on register
COMPANY RECORD · company-public.json v1
  • ax0s-memory implemented public release record pending
  • Evidence publication policy Method published · 2026-07-14
  • Self-hosted data boundary Verified 2026-07-14
  • Security page publication pending
  • Notes page publication pending

Source · company-public.json · read at build time

01 · Founders

Two sides of one problem.

Chris takes the problem into the product. Aaron takes it into the business. Both of them are on your call, and both of them stay on the work.

Chris Blaschke

Founder & CEO · Technical Lead

Chris Blaschke

Chris leads the product and engineering behind AX0S.

He came out of commercial leadership, watched company knowledge scatter across tools, and now builds the store that holds it. He works on the deployment with the team that runs it.

Owns · product, engineering, the register

Accountable operator for the AX0S product and evidence-publication boundary.

Aaron Dyson

Co-founder & CRO

Aaron Dyson

Aaron leads customer strategy, partnerships, and the commercial side of AX0S.

He helps a team name the question that keeps coming back, find the systems behind it, and scope a first deployment with an outcome someone can check.

Owns · strategy, partnerships, first deployments

Commercial counterpart on design-partner engagements.

02 · How we work

The people who hear it are the people who build it.

One problem goes to 2 operators and comes back as scoped work. There is no second team waiting behind the call.

Chris · into the product Aaron · into the business
One question you answer by hand Work scoped with you
Sales team Delivery team Does not happen here
FIG.1 · one problem, 2 operators, one scope dashed = the handoff we do not run
01 No handoff The two people who hear the problem scope it, build it, and answer for it.
02 One bounded test first One question, one trusted source, acceptance criteria written down before the work.
03 Self-hosted by default The data boundary sits on machines you run. Verified 2026-07-14.
04 Limits are published Every claim carries its scope, its date, and the line it does not cross.
What the product does Capability register Integrations checked 2026-08-23

03 · What we publish

Four company records, and what each one is missing.

AX0S intends to publish methodology, null results, and killed ideas as part of its evidence policy. This states a publication intent; methodology, null-result, and killed-idea artifacts remain sparse or unavailable.

Record Status Date

Self-hosted operating-memory boundary

The linked page describes the product boundary; a dated release record is not yet published.

implemented public release record pending Not yet published

Public claim register status

No evaluation value or dated methodology artifact is published.

rerun pending Not yet published

Website privacy boundary record

The page records the current operational boundary and is pending formal legal review; it is not presented as a reviewed privacy notice.

current boundary record pending formal legal review Effective 2026-07-14

Website terms boundary record

The page records the current website terms boundary and is pending formal legal review; separately reviewed service terms are not published.

current boundary record pending formal legal review Effective 2026-07-14

A record without a date and a method does not go on this site. When a number lands, it lands on the register with its scope and the day it was checked.

Talk to us

Bring one question. Meet both founders.

Thirty minutes, no deck. The booking page holds the calendar and the fit rules.

chris@ax0s.io · Ax0s, LLC