---
title: "Careers · Frazer"
description: "Help build the AI-native cloud for people who build real things: how we work at Frazer, and how to reach us."
url: https://frazer.ai/careers
index: https://frazer.ai/llms.txt
tokens: 415
---

> For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt.

# Careers · Frazer

**Careers**  frazer.ai

# Help build the cloud  
for people who build real things.

Frazer is a complete cloud with a ready-to-go IDE, built to run on real servers. This is how we work, and how to reach us.

[Write to us](mailto:support@frazer.ai?subject=Careers) [About Frazer](https://frazer.ai/about)

01 · How we work

## The rules we build by.  
On our own platform first.

-   ### Every change is a plan
    
    A write by a person, an agent or Frazer itself is a plan with an audit entry. Our own infrastructure is code, reviewed before it is applied.
    
-   ### Two people for every change
    
    Infrastructure changes need two approvals, and the person who approves an agent’s pull request is never the one who sent the agent.
    
-   ### Postmortems without blame
    
    An incident ends with a blameless postmortem and action items with deadlines.
    
-   ### Agents under the same rules
    
    Agents act under their own identity, inside budgets and approvals. An agent never approves anything.
    
-   ### Facts before adjectives
    
    We publish a number only when we can source it.
    
-   ### We run on what we sell
    
    Our probes and alerts are the first customer of Frazer’s monitoring, and our clusters run the same Security Center.
    

02 · Open roles

## No open roles listed.  
Write to us if you want to build Frazer.

How to apply

Write to [support@frazer.ai](mailto:support@frazer.ai?subject=Careers) with “Careers” in the subject.

## From one core to a thousand agents.  
And why it stays manageable.

[Read the essay](https://frazer.ai/evolution) [About Frazer](https://frazer.ai/about)