Omnishown Blackbox · Safety and control
Changes you can read, approve and undo.
Blackbox 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
Omnishown: add FAQ answers to /menu
Pull request #14
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, Blackbox 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
main · branch protection
Merge rules you already own
- Omnishown CheckRequiredPassing
- Build and testsRequiredPassing
- 1 approving reviewRequiredWaiting
Example. You choose which checks are required in GitHub.
The small, specific fixes.
Blackbox 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
- 4
− <title>Home</title>Says nothing about what you sell or where - 4
+ <title>Sweet Crumbs | Custom cakes, Gachibowli</title> - 5
+ <meta name="description" content="Same-day custom…">Gives search and AI a one-line summary - 9
<body> - 10
+ <script type="application/ld+json">{"@type":"Bakery"…}Tells engines you are a local bakery, with hours - 42
+ <section id="faq">…</section>Answers the questions buyers ask AI
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
Omnishown · Client sites
Every client, one queue
- bloom-florist/sitePassed
- rao-associates/site2 fixes ready
- green-leaf-cafe/sitePassed
- fitwell-studio/site1 fix in review
Example client names, not real customers.
What is recorded for every change.
- 1
The recommendation
What was suggested, the evidence behind it and who approved it.
- 2
The patch
The exact diff and the result of the checks run on it.
- 3
The pull request
The branch, the pull request and whether it was merged.
- 4
The way back
Because every change is a normal commit, it can be reverted like any other.
What Blackbox 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 Blackbox 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