Octopus AI · Safety and control · In build
Changes you can read, approve and undo.
Octopus AI is built so that nothing reaches your live site without a person saying yes. Every change is a small pull request with a reason, a record is kept of what happened, and your data stays separate from everyone else's.
- Pull requests, never direct edits
- Small patches, checked before they open
- A record of every step
- 1Patch
- 2Isolation check
- 3You approve
- 4Pull request
- title: "Home",
+ title: "Custom cakes in Hyderabad | Sweet Crumbs",
Audit log
- 10:02:11recommendation approved · homepage title
The record
What is recorded for every change.
Each change leaves a trail you can read later: what was suggested, what was changed, where it went, and how to take it back.
SEORewrite the homepage title
Evidence: the title on / is “Home”. It says nothing about cakes or Hyderabad.
Record
- RecommendationRewrite homepage title · approved by you
- Patchapp/layout.tsx +1 −1 · checks passed
- Pull request#14 · omnishown/fix-homepage-title · merged
- Way backRevert available as a normal commit
From approval to merge, in your hands.
You install the Omnishown GitHub App on the repositories you choose and pick a target branch. For each recommendation you approve, Octopus AI finds the relevant file and drafts the smallest patch that does the job.
The patch is checked in an isolated process, you see the diff, and only then is a branch and pull request opened. You or your developer review and merge it, and your normal deployment takes it live.
- Install on the repositories you choose
- Approve a recommendation
- Review the diff
- Merge and deploy your usual way
Repositories this app can see
- sweetcrumbs/sitetarget: main
- sweetcrumbs/blog
- sweetcrumbs/internal-tools
Every approved change
- Approve
- Find file
- Draft patch
- Check
- Pull request
- You merge
The last step is always a person. Your usual deployment takes it live.
The small, specific fixes.
Octopus AI is aimed at changes that are easy to review: page titles and meta descriptions, canonical tags, sitemap and robots settings, structured data, internal links, Open Graph tags, and content edits you have approved.
It does not rewrite whole files. If a change cannot be expressed as a checked, minimal patch, it is not proposed.
- Titles and descriptions
- Canonical, sitemap and robots
- Structured data and Open Graph
- Internal links and approved content
- Title
- Description
- Canonical
- Robots
- Structured data
- Internal link
- Open Graph
app/layout.tsx+1 −1
- title: "Home",
+ title: "Custom cakes in Hyderabad | Sweet Crumbs",
Whole-file rewrite · never proposed
Kept separate, handled on the server.
Each organisation's projects are isolated from every other organisation's. Keyword data and your own site data are kept logically apart.
Sensitive work happens on the server. Your browser never holds GitHub credentials, private keys or access to the keyword index.
- Isolation between organisations
- Credentials stay on the server
- Least-privilege GitHub permissions
Sweet Crumbs
- Projects
- Site data
- Approvals
Cross-org read refused
Brightline Dental
- Projects
- Site data
- Approvals
Server only
- GitHub credentials
- Private keys
- Keyword index
What Octopus AI will not do.
- It will not push to your production branch directly.
- It will not overwrite a file wholesale.
- It will not deploy for you. Your existing process stays in charge.
- The exact GitHub permissions, storage and retention details are published on the security page before any pilot repository is connected.
Questions, answered plainly
Still unsure? Join the pilot and ask us directly. We'll answer before you connect anything.
Can Octopus AI change my live site on its own?
No. Every change is a pull request. Your site changes only when someone merges it, and your own deployment process takes it live.
What if a merged change causes a problem?
Every change is an ordinary commit, so it can be reverted in GitHub like any other, and the record shows what was changed and why.
Which frameworks does it support?
Support starts with a small number of frameworks and grows from there. Tell us what your site is built with when you join the pilot.
Will enterprise teams be able to automate approvals?
That is an open decision. Today the default is that a person approves every change.
Stay in charge of every change.
Join the pilot and ask us anything about access and safety before you connect a repository.
- No card, no commitment
- Every fix arrives as a pull request you approve
- Planned pricing from ₹2,999 per site per month