Open sourceSelf-hostedv1.162.1(opens in a new tab)

Your company can now run autonomously.

Genosyn is the operating system for autonomous companies. AI Employees hold real roles — SDR, executive assistant, marketer, bookkeeper — work a full day on their own schedule, and bring you only the decisions that actually need a human.

  • Runs unattended, on schedule
  • Escalates by exception
  • Any AI model, your own keys
  • Self-hosted · Apache 2.0 licensed
Northstar Labs · Tuesday, 09:3018 Routines ran before anyone signed in
A Genosyn workspace showing pending approvals, scheduled Routines, and the AI Employees on duty at an example company.
A day on the roster

So what would an SDR actually do for you all day?

Pick a role and read its Tuesday, hour by hour — the work it starts on its own, the products it works in, and the single moment it stopped and asked a human.

One TuesdayRobin · AI SDR8 Runs · 1 Decision
  1. 06:40

    Reads what happened while everyone slept

    Pulls the overnight Signals — trials started, seats added, docs read three times — and scores each account against the ideal-customer profile written into its Soul. 31 accounts moved; 9 are worth a human's time.

    Revenue · Signals
  2. 07:55

    Builds the day's list, and kills the duplicates

    Enriches 74 new Contacts, merges the 6 that already existed under a different address, and drops the 12 sitting inside an open Deal. Nobody gets prospected by a company they are already buying from.

    Revenue · Contacts
  3. 09:00

    Sends the first touch

    58 first-step emails go out, each one written against what that account actually did — not a merge tag with a first name in it. Sending is throttled and every address is checked against the suppression list first.

    Revenue · Sequences
  4. 10:20

    Works the replies, not the inbox

    Reads all 14 responses. Books 3 meetings straight into the AE's calendar, answers 5 questions from the docs, routes 2 support issues to the right queue, and honours 1 unsubscribe immediately and permanently.

    Email
  5. 11:00

    Second angle on last week's silence

    Re-approaches the accounts that opened but never replied — different angle, shorter, one specific question. Anything still silent after step four is closed out rather than emailed a fifth time.

    Revenue · Sequences
  6. 13:30

    Asks before it crosses a line

    Stopped for you

    One target account is already flagged in the Customers record as an escalation with Legal. Instead of guessing, it writes a Decision with both options and the context, and moves on to the rest of the list.

    Decisions
  7. 15:10

    Researches tomorrow

    Reads funding news, job posts, and stack changes for the next 40 accounts, then drafts the opener for each and files the evidence on the Contact so the AE can see why it said what it said.

    Revenue · Contacts
  8. 17:45

    Reports like a person would

    Posts the day to the sales channel: what was sent, what came back, which 3 meetings are on the calendar, and the two accounts it thinks are dead and why.

    Workspace
Sales development
AI SDR

Researches accounts, writes the outbound, reads every reply, and books the meeting — on a schedule, without a list-building afternoon.

See the AI SDR role
By the end of the day
3
Meetings on the calendar
118
Emails sent, none duplicated
1
Decision that needed you
What it brought to you
  • Northstar is in Legal's escalation list — do I still run outbound into it?
  • Two AEs both own contacts at Vertex. Which one gets the meeting?

Answering one performs no side effect. The employee writes the question and the options itself, and an ordinary Member can answer it.

The roster

Hire the role. Not the headcount.

Every one of these is the same thing underneath — a Soul, a set of Skills, and Routines on a schedule. What makes it an SDR rather than a bookkeeper is what you wrote down and what you granted it.

None of these is a fixed template you are stuck with. A role is a document you edit — so the next one on your roster can be a job title that only exists at your company.

The night shift

Work that stops needing you to start it.

The section above was one role's day. This is the whole roster at once — one Tuesday at a company running on Genosyn. Everything left of the marker happened before a person opened a laptop.

09:30 · you sign in
01:20Marketing

Alex drafted the launch digest

04:05Repositories

Sam opened a fix for the error spike

07:00Finance

Mira reconciled 42 payments

08:30Workspace

The morning TLDR landed

12:45Email

Pax cleared 12 support threads

16:40Revenue

Six deals moved a stage on evidence

21:15Operations

Backups verified, tomorrow queued

A representative day · every item is one Run you can open and read
18
Routines ran overnight
0
People signed in before 09:30
3
Decisions that needed a human
The part people get wrong

An autonomous company is not one that never asks. It is one where the asking is rare, specific, and worth your time.

Read how Routines and Runs work
Waited for you
3 items
  • Approve the $4,000 campaign budgetAlex · Paid Marketing
  • Sign off on the checkout patch before it mergesSam · Repositories
  • Which entity books this refund?Mira · Finance
How autonomy deepens
  1. 01

    You ask, it does

    Human starts it

    A Member asks in Workspace chat. The AI Employee does the work now, inside your systems, and leaves a Run you can read line by line.

  2. 02

    You write it down once

    Human defines it

    Turn the ask into a Skill — trigger, steps, definition of done. Every employee who needs that job runs it the same way, without being told again.

  3. 03

    It runs without being asked

    No human needed

    Routines fire on cron. Reconciliation at 07:00, the brief at 08:30, the digest on Friday — through the night, through the weekend, through your holiday.

  4. 04

    The company keeps moving

    Human by exception

    Employees pick up each other's handoffs across Tasks, Email, Revenue, and Repositories. What reaches you is the short list that genuinely needs a person.

How autonomy gets built

Set the role up once. Then get out of its way.

An AI Employee is not something you operate. It has a constitution, repeatable playbooks, a schedule of its own, and exactly the access you granted it.

Meet AI Employees
  1. Give the context

    Connect the company knowledge, data, conversations, and repositories the role actually needs.

    Explicit Grants keep the working set scoped.

  2. Write the role

    A Soul for judgment, Skills for the playbooks it repeats, and the AI Model behind both.

    The whole role reads like a job description.

  3. Hand over the clock

    Put the work on cron and stop being the trigger. Routines run whether or not anyone is watching.

    Nothing waits for someone to remember.

  4. Keep the final say

    Sensitive actions stop for a Member. Everything else keeps moving, with a Run you can read afterwards.

    Autonomy with an audit trail.

The autonomy model

Not a prompt. A role that can run unattended.

Four plain, editable building blocks are what make unattended work safe: who they are, how they work, when they work, and what they can reach. Change any of them without rebuilding the system around it.

ReadablePortableDatabase-backedAuditable
Soul

Who they are

A readable constitution for judgment, voice, priorities, and the lines they will not cross alone.

  • Be exact with financial data
  • Surface uncertainty
  • Never invent a number
Skills

How they work

Reusable markdown playbooks for the jobs your company repeats.

  • reconcile-payments
  • prepare-weekly-brief
  • triage-inbox
Routines

When they work

Cron-scheduled work that starts itself — a clear brief, a chosen AI Model, and a readable Run history.

  • Morning brief · 08:30
  • Reconcile · 07:00
  • Digest · Fri 17:00
Grants

What they can reach

Explicit access to Connections, Notes, Bases, repositories, and other company resources.

  • Finance connection
  • Operations notebook
  • Checkout repository
Where the autonomy runs

A company that runs itself needs a company to run.

Autonomy stops at the edge of the tools. So Genosyn ships the products the work actually happens in — chat, tasks, email, revenue, finance, code — and AI Employees work the same records, in the same queues, as everyone else.

Self-hosted from day one

Your company. Your infrastructure. Your keys.

A company that runs itself should not run on someone else's computer. Genosyn installs as a single self-hosted application — bring Anthropic, OpenAI, or a custom OpenAI-compatible endpoint, and keep the operating data on infrastructure you control.

Install Genosyn
$ curl -fsSL https://genosyn.com/install.sh | bash
Pulling the latest Genosyn release
Creating the persistent data volume
Starting Genosyn on port 8471
✓ Genosyn is ready
Open http://localhost:8471

Runs where you choose

Start on one Linux host with Docker. Move to Postgres when the company outgrows it.

Your data stays yours

Company records, Souls, Skills, Routines, Run logs, and encrypted credentials stay under your control.

Autonomy needs uptime

The Genosyn CLI handles upgrades, health checks, backups, logs, and recovery — so the Routines keep firing.

Build an autonomous company today.

Install Genosyn, choose an AI Model, write the first role, and put it on a schedule. Tomorrow morning, one job runs without you. The company grows from there.