AI at the core, not bolted on
An agent graph with a model chosen per node — routing, extraction, conversation, retrieval. Long-term memory that survives across sessions. Voice runs on the same tools as text.
AI-native software · ARE5 Technologies LLC
Systems that act, under proof.
ARE5 Technologies is a US software company. We build systems where an AI agent does the work a person would otherwise do by hand — running operations inside a company's own business software, building and publishing a website, holding a person's context over years — and a deterministic layer in front of the agent records every action before it happens, not after. Crafty publishes live sites for people outside the company; AIO runs our own operations, with no outside tenants yet; X-Zero is in development.
01
Products
Status is stated as it is. Production means the system runs on real data and serves people outside the company. Internal means it runs in production on our own operations only. Development means not yet running.
AIO
Enterprise
An AI layer over enterprise resource planning. The business talks to its own system by text or voice, and the agent performs the operation under a deterministic control layer. Running in production on our own company's operations today; opening to first pilot customers.
Inside
A deterministic layer sits between the agent and the ERP. It records what the agent intends to do before the action rather than what happened after it, and a separate nightly process reconciles that record against the live system. Twenty-six ERP operations are exposed as tools; irreversible ones are classified by tier, not by tool name. Enforcement is currently in observation — the layer classifies and records, and does not yet refuse.
Production · internal→
Crafty
Consumer
A platform for launching and running sites, not a page builder: templates with a theme system, editing in place, publishing to our own CDN, and an SEO engine, analytics, storage and leads in the same admin.
Inside
The site is data, not a folder of files: content lives in a structured store, and publishing renders it to static pages served from a CDN. The editor writes into the same store the renderer reads, so what you edit is what ships. Design tokens are semantic — a colour is never a hex in a component — which is why a theme change is one edit rather than a search across the codebase. The codebase carries 121 test files, more of them than anything else we run. Release is queued behind AIO, and the product site is being redesigned.
Pre-release · redesign→
ARE5
X-Zero
Personal
An agent bound to one person rather than to a company: memory that accumulates over years instead of resetting each session, reachable by voice, acting under the same control layer the enterprise products answer to.
Inside
The difference from an assistant is the horizon. A session-bound assistant starts over every time; this one is meant to hold years — what you decided, what you rejected, and why — so the useful answer is the one that remembers the last three. Twenty-seven screens are built on a settled architecture with the test suite green, and the agent channel to our engine is already wired, which is why the remaining work is specific: deciding which of its surfaces genuinely need a server, and connecting those to the graph, memory and control layer the other products already run on. It inherits all four rather than reimplementing them — the reason a fourth product is a configuration and not a rewrite.
In development→
02
What is underneath
One engine behind every product. Three properties carry it; everything else is configuration.
Every action leaves proof
A deterministic layer decides whether a specific operation is allowed right now, and writes what it is about to do and why — before the action, not after it. Records are immutable.
Not locked to one cloud
The orchestration layer deploys as a managed runtime on more than one provider, and the infrastructure is defined as code — so the stack is reproducible rather than tied to a vendor.
03
Questions we get asked
The five that come up before any call. Answered here so nobody has to spend a meeting on them.
- What does the control layer actually do?
- It decides whether a specific operation is allowed at the moment it is requested, writes what it is about to do and why, and only then lets it run. The record is written before the action, so a refusal is as traceable as an approval, and the records are immutable.
- Which products are in production?
- One of three serves people outside the company: Crafty publishes their sites. AIO runs in production on our own operations — we are its first tenant, which is how the rough edges get found before a customer meets them. X-Zero is in development, and we say so rather than listing it as available.
- Is this one product or three?
- One engine, three products. The agent graph, the control layer, memory and voice are shared; each product is configuration on top of them, not a separate codebase.
- Can it run outside AWS?
- Yes. The orchestration layer deploys as a managed runtime on more than one provider and the infrastructure is defined as code, so the stack is reproducible. Primary infrastructure runs on Amazon Web Services in the United States today.
- Who is behind the company?
- ARE5 Technologies LLC, a company registered in Wyoming in 2026 and operated from Bangkok. Bootstrapped, no outside round, founder-led — an email to ceo@are5.ai reaches the founder directly, because there is no account manager to route it through.
04
Company
A US company operating from Bangkok. Bootstrapped, no outside round, a very small team.