AI-native operating system · ten founding installations

We install the operating system your company's AI runs on.

One maintained library of what the company knows, the skills that turn it into work, your tools connected, and the rules for what an agent may do without asking. Across GTM, engineering, the marketing site and ops.

$5,000 once, normally $10,000. Ten companies, then this closes September 1.

One library, every agent

One library. Every agent starts there.

Your pricing, positioning and rules live in one place. Agents read that first. Changes wait for a person.

  • Always loaded. The docs every agent sees.
  • On demand. Pulled in when the question needs them.
  • Never exposed. Drafts stay private.

Works with the agents you already use

Claude Code. Same library. Same rules.

Notara · AcmeLibraries
Skills

Good prompts become team skills.

Save the prompt with the tools and context it needs. Anyone on the team can run the same version.

Approvals

Writes wait for a person.

Reads run right away. Writes wait for approval in Slack. Deletes need an admin. Every decision is logged.

What your team actually runs.

Skills, shared context, schedules and the right access for each group. Not another chat window.

01

Turn good work into a skill

Save the prompt, the tools it may use and the context it needs. Anyone on the team can run the same playbook.

02

Read the company library first

Agents see what exists, then open only the docs the task needs. Less guessing. Fewer conflicting answers.

03

Run the work on a schedule

Run the same skill every morning, every Tuesday or at month-end. Results land back in the library for next time.

04

Give each group its own scope

Marketing gets its own library and skills. A contractor can use that scope without seeing everything else.

05

Connect your tools, or use ours

Bring your own keys, or run scraping and research on Notara's. Pay for what you use. Skills call the tools. You don't need a separate subscription for every vendor.

Skills call the toolsYour key or ours
How it works

Teams build01 a first library, connect02 Slack and their agents, and choose03 what needs approval.

01

Build the first library

Paste your website. Notara drafts a first library. You fix what it got wrong. That becomes what every agent reads.

02

Connect Slack and your agents

Invite Notara to Slack. Or connect Claude Code, Cursor or your own agent. Same library. Same rules.

03

Choose what needs approval

Mark each action as read, write or delete. You pick what needs a person. Approvals land in Slack. Every decision is logged.

What keeps the library current.

Six controls so the shared context does not go stale after week one.

01

What loads first

Choose what always goes in, what is searched when needed, and what never reaches a model.

02

Library index first

Every agent sees what exists in the library before it opens a document.

03

Versioned skills

See what changed in a team prompt. Roll back if you need to.

04

Read, write, delete

Tag every action, then attach the right rule. Writes wait for a person.

05

Audit log

Every write records who asked, what changed and how it resolved.

06

Fresh sources

Refresh crawls and research from the source on a schedule.

Pricing

Ten installations at half the published price.

There are no external paying customers yet. You would be among the first, and ten real installs teach us more than another month of building will. That is the whole reason for the number, and on September 2 it goes back to $10,000.

Waitlist

For everyone after the tenth slot goes
Free
No card, and no date promised
Join the waitlist
  • No card, and no date promised
  • You hear first when installations reopen
  • The published price applies when they do

Founding installation

Most chosen
Ten of them. We install it inside your company and hand it over running
$10,000$5,000 once
Then $149/month + $29 per seat, locked at that rate for as long as you stay
Take a founding slot
  • Your context crawled and structured into working collections
  • Your tools connected, your keys or ours
  • Slack wired, and one scoped endpoint any agent can read through
  • The skills your team actually runs, authored and versioned
  • Approval rules set once, and every call logged
  • Four hours live in your stack, a written recap, one week of support

Starts at $149/month + $29 per user after installation, with fair-use AI limits. Enterprise plans available for SSO, security reviews and higher usage caps.

No SLAs, no dedicated staff, and no custom development inside the fee. Notara does not hold SOC 2; the hosting provider does. The MCP endpoint is read-only today.

Three things run out, in this order.

The install date
Ten slots, and we install in the order people pay. Slot one starts the week of August 24. Slot ten starts in October. The queue does not get reshuffled, so waiting a week is not waiting a week. It is a later start.
The price
$5,000 until September 1. On September 2 it goes back to $10,000, which is what this page said yesterday and what it will say again.
The founding rate
The subscription is $149 a month plus $29 per seat. Founding companies keep that rate for as long as they stay. That one does not come back at any price, on any date, for anyone.
Done for you · Notara Installation

What the installation actually covers

We build the library, connect the tools and write the first skills with your team, inside your real stack. Then you keep running it without us.

Not included: no SLAs, no dedicated staff, no custom development. Only what is true and already built.

Co-founders twice before this: SwiftPad, acquired by MedAvail, and Blackcreek. You work with us, not a delivery team.

Built by the two of us

Amir M
Amir M
Context, skills, approval model
Two exits · AI products at IBM Garage · strategy at Sun Life · teaches AI-native ops
Max A
Max A
Connectors, endpoints, agent surfaces
SOC 2/HIPAA health platforms at imaware (100k+ users) · UX lead at Sun Life
01Before we start

Scope

We agree the work on a call and write a one-page scope. Nothing is provisioned or paid until that is signed.

  • A call, not a form
  • One-page scope doc
  • No access before paper
02The build

Built in your stack

We structure your context, connect tools, wire Slack and your agents, and write the skills your team will run.

  • Context structured into collections
  • Connectors on your keys or ours
  • Slack and agents scoped per group
  • Skills written and versioned
  • Read, write and delete rules
03Then it is yours

Handover

Up to four hours live, a written recap, and one week of support. After that it runs without us.

  • Four hours live
  • Written recap
  • One week of support

Ten installations at $5,000, closing September 1. Then it goes back to $10,000. We scope it before you pay.

Book an installation call