Build a team of AI agents that works while you sleep.

Yes. The framework behind Night Owls is the @nightowlsdev/* packages on npm, MIT licensed: the engine, the chat UI, the runners, and the model and storage adapters. Self-host it on your own infrastructure with your own keys, billing, and ops, there is no license fee and no seat cost, you only pay your own providers for the tokens a run actually uses. The hosted workspace at getnightowls.com is a separate, optional layer on top, ready-made space templates, a credit wallet, and managed infrastructure, but you never need it to run the framework.

Owl Credits are the one currency for usage: one credit is worth $0.01, so 1,000 credits is $10, and a workspace only spends them while a crew is actually working. A typical turn on the current crews costs 1 to 10 credits, and every turn is capped at $0.50 before it pauses and asks rather than running further. You see the reserve when a run starts, the live spend while it works, and the settlement when it ends, and if a run ever fails to deliver what you asked, its credits are refunded in full.

No. Any side-effecting action, sending an email, filing tasks, or anything else that leaves the conversation, stops and waits for your approval first. This gate is on by default and cannot be turned off, on hired templates, on connected tools, and on agents you define yourself. A crew can research and draft freely; it just cannot act on your behalf without your yes. Spend caps limit cost, the approval gate limits consequences, and you control both, separately.

Yes. Night Owls is an open-source TypeScript framework underneath, the @nightowlsdev/* packages, MIT licensed, that you can run on your own infrastructure with your own model and storage providers. Self-hosting gives you the same engine, the same chat UI, and the same non-removable approval gate; you bring your own keys, billing, and ops. The hosted workspace adds the credit wallet, the ready-made space templates, the connector vault, and managed infrastructure on top. Same framework either way, the choice is how much you want to run yourself.

We do not train models on your data. Conversations and a crew's memory are scoped to the workspace and thread they belong to, and a crew never reads another thread, another space, or another workspace. Connecting an outside tool, like an inbox, goes through a per-user credential vault with OAuth; keys stay server-side and are never handed to the model. Untrusted content from inboxes, documents, or the web is fenced, and the approval gate is your backstop against anything acting on an injected instruction. AI work is labeled as AI work throughout the product.

Crews run on leading models, reached through adapters for Anthropic, OpenAI, OpenRouter, and the Vercel AI Gateway. You are not asked to pick a model by name: a cheaper, fast model is the default for everyday work, and frontier-tier models are used where a crew's role calls for them — they simply spend the same prepaid credits faster. Overspend protection comes from the wallet being prepaid and from the $0.50 per-turn cap that pauses and asks, not from a model paywall. If you self-host, you wire up whichever providers and keys you want, including Groq's fast inference and fully local, no-key models through Ollama.

Yes, a space is yours to compose. Start by hiring one of the five shipped templates, General, Content Studio, Inbox Concierge, Writer, or Marketer, then shape the crew in the studio: define a new agent, its role, instructions, and model, review it before it publishes, assign it to the space, and choose which agent is the Chief. Nothing rewrites itself behind your back, and every agent you define sits behind the same non-removable approval gate as the shipped ones. If you want to build completely freely, the framework is open source and self-hostable, and ready-made agents including a researcher already ship in it.

Not yet, and we would rather say so plainly: the hosted workspace is invite-only while we run the first cohort. Join the waitlist from the band at the end of this page and we will send an invite as spots open, in small batches. Invites go to a specific email address, so use the one you want the workspace on. Nothing about the framework is gated: the @nightowlsdev/* packages are MIT licensed and self-hostable today, no queue, if you would rather run it yourself.

Yes. Opening a workspace gives you 1,000 free credits, no credit card required, once, on signup. The grant spends like any other credits: everyday work runs on the default, cost-efficient models, and where a crew uses a frontier-tier model it simply draws the balance down faster — with every turn still capped at $0.50 before it pauses and asks. There is no time limit and nothing to cancel while you are on it. When you want more capacity, you top up credits, entirely your call.

Yes. There is no contract and no card required to start, so on the free grant there is nothing to cancel, just stop using it. If you have topped up credits or taken an optional subscription, you can stop renewing whenever you like and keep using the credits you already own. Purchased credits are non-refundable, non-transferable usage credits, and they expire 12 months after your most recent top-up; any new top-up re-extends the whole balance. We will tell you clearly before anything changes.