Procedures live in docs
SOPs written in Notion or Confluence never reach the tools they describe. Someone still has to translate them into action manually.
AI Operations Partner
Your procedures, deployed.
Your procedures, deployed.
Every action, approved.
Oky reads your SOPs, refines them through conversation, and runs them against your real tools — stopping before every write for your go-ahead.
100%
Write actions require approval
0
Lines of code to connect a tool
∞
SOPs per workspace
Slack
Notion
HubSpot
GitHub
Salesforce
Gmail
Your data
What Oky does and how it uses Google data
Oky is a business productivity application. Employees of customer companies connect their work accounts so Oky can find information in their email, files and calendar, and run operational workflows they configure and approve, such as consolidating a report from spreadsheets and emailing it to the team.
When you connect Google Workspace, Oky only accesses the Gmail, Drive, Calendar and Sheets data covered by the permissions you grant, and only to run the tasks you or your organization request. Oky's use of data from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This data is never sold, used for advertising, or used to train general-purpose AI models.
Oky has no image-generation or image-editing features and never uses Google APIs, or data obtained through them, to create or alter sexual or intimate imagery of any person, including AI-generated non-consensual intimate imagery (NCII).
The gap
Your team runs on procedures.
Your team runs on procedures.
Your tools don't know that.
Automation runs unsupervised
Zapier and Make execute flows without judgment. One misconfigured step can affect real customers before anyone notices.
Agents act without control
AI agents can reason and plan, but nothing stops them from writing to production systems autonomously. "Trust me" is not a governance model.
The solution
Write the procedure. Oky runs it.
Write the procedure. Oky runs it.
You approve every action.
1
Write your SOP
Draft your procedure in plain markdown in Oky's workspace. Describe what should happen, when, and what to do if something goes wrong.
2
Oky refines it
Oky reads the draft and asks clarifying questions, one at a time, until the procedure is unambiguous and machine-ready.
3
Test in sandbox
Deploy to sandbox. Run it against live systems in a controlled environment. See every step execute before it touches production.
4
Go live
Promote to production. Your procedure runs automatically whenever its trigger fires — and stops at every write action for your approval.
New lead intake
When a new lead submits the contact form, check whether they already exist in HubSpot — and only create a record if they are genuinely new.
- Look up the lead by email address in HubSpot.
- If they already exist, stop here and log the match. Nothing is created.
- If they are new, draft a contact and assign it to the owner for their region.
- Ask me to approve the new contact before anything is written. Approval required
- Once approved, create the contact and post a note to the owner in Slack.
Always ask before creating or changing anything.
The prose is yours. The execution is Oky's.
Use cases
Built for how your business actually runs.
The same platform, tuned to each operation — every write paused for approval.
Law firms
Deadlines, LGPD, clients under control
Court deadlines, LGPD requests, and client intake — every write paused for your approval.
See the caseAccounting
The fiscal calendar, handled
Fiscal calendar, document collection, and payroll — nothing is filed without your sign-off.
See the caseReal estate
Grow without losing the timing
Lead response in minutes, 40+ documents tracked, and commissions approved before any payout.
See the caseCustomer case · Armazém Auto Peças
Six departments on AI, no new headcount
How one auto-parts operation runs six departments with AI — growing without adding staff.
See the case
The invariant
Every write action stops.
Every write action stops.
Every time. No exceptions.
This is not a setting. It is an architectural invariant, mandatory by default. Oky can read data, analyze systems, and plan actions autonomously. It cannot modify anything — send a message, create a record, update a field — without your explicit confirmation. Those with permission can define auto-approval for low-risk actions.
Human-confirmed
Every write routes through the Gate by default. You choose what can auto-approve.
Auditable
Every approval decision is logged. Who approved, what they approved, when.
Bounded
A workspace problem stays bounded to that workspace. Resource isolation at every layer.
Connect everything
Oky acts where your work happens.
Slack
Gmail
Google Calendar
HubSpot
Salesforce
Notion
GitHub
Linear
Stripe
Airtable
Zapier
Intercom
+ build your own with the connector SDK
Run your operations with confidence.
Join the early access list. We onboard teams manually — you will talk to a founder before your first SOP goes live.
No credit card. No self-serve setup. We start together.
Thanks — you're on the list. We'll reach out from a founder's inbox.