Discovery
We spend time with the people currently doing the work. We count how often it happens, how long it takes, where it goes wrong, and which decisions genuinely need a human. You get that written down whether or not you hire us.
Platform
Build it. Run it. Bill for what it did.
Auth Alien is not a delivery shop. We engineer a system around a specific piece of your work, deploy it inside your infrastructure, operate it around the clock, and meter what it produces.
Discovery
Engineering
Deployment
Operation
Metering
The lifecycle
Dock a phase.
Drag the ring, click a phase, or use the arrow keys. Each phase expands into the three things that actually happen inside it.
Build · Run · Bill
drag · click · arrow keys
Stage by stage
What the first year looks like.
Engineering
We build against your real data model and your real tools — not a demo environment. Approval rules, escalation paths and audit requirements are part of the design, not a later phase.
Deployment inside your stack
The system is installed on infrastructure you control. Credentials stay in your vault, payload data stays inside your boundary, and the whole thing can be shut off from your side without calling us first.
Operation
We run it. Health checks, queue depth, error budgets, upstream changes, and the 3am pager are ours. You get a weekly note in plain English and a call when something needs your decision.
Metering
Every completed action is recorded against a unit you agreed in discovery. Retries, failures and idle time are never billed. The invoice reconciles to rows you can query yourself.
Inside your stack
Your infrastructure. Your data. Your off switch.
Self-hosting is not a premium tier here — it is the default posture, because it is the only honest answer to “where does our data go?”
- Where it runs
- Your cloud account, your cluster, or hardware in your building. your boundary
- Where data rests
- In the stores you already operate. We add no new copy of your records. no exfiltration
- What we hold
- Operational telemetry and the metered action count — never payload contents. counts only
- How it stops
- You revoke our access and the system keeps running, or you stop it. Both are one action. your control
Operated by us
“We run it” is a commitment, not a slogan.
Monitoring that reaches a person
Health probes, queue depth and error rates are watched continuously. Alerts route to an engineer who can actually change the code, not a triage queue.
Upstream change is our problem
Vendors rename fields, rotate credentials and tighten limits without warning. Absorbing that is part of running the system, not a change request.
Improved on a monthly rhythm
Work changes shape. Every month we look at what the system got wrong, what it escalated, and what it should now be allowed to decide alone.
Start with the work, not the software.
Describe one process that runs every day and annoys everyone. Discovery tells you what it costs today and what a deployed system would meter.