What happens to your code_
Read this before you connect a repository. Every sentence on this page is true today; where a control does not exist yet, it says so.
Read-only GitHub app · first run on us · no card
Read-only, scoped.
The GitHub app requests read access to code and metadata for the repositories you select. No write access, and no organisation-wide access unless you choose it.
One sandbox per run, then gone.
Your repository is cloned into an isolated, single-use sandbox that is destroyed when the run ends. What persists is the report, the artifacts and the run log — which can include excerpts of files the workflow read — and nothing else.
90 days, or less if you say so.
Reports, logs and artifacts are kept for 90 days (a year on Pro and Team) and deleted on request, or when you delete the project.
Commercial API access, no training opt-in.
Runs use Midkernel's commercial API accounts with the major model providers. We do not opt in to any provider training programme. The model sees your code only as part of the run, and the model and version are recorded on every run.
Every run pins its inputs.
Repository commit, workflow commit, profile, model version and sandbox image are recorded on the run and shown in the report.
Egress limited to what the workflow needs.
Sandboxes can reach the model provider and package registries. Workflows declare any other host in their manifest, visible before you run.
Who can see what.
Reports are visible to the members of your workspace. Midkernel staff open a customer's run only for a support request you filed, and the access is recorded.
- sandboxes
- isolated single-use sandbox infrastructure
- hosting
- Vercel
- DNS
- Cloudflare
- database
- managed Postgres
- models
- major model providers, per profile
- Resend
- payments
- a card processor, named in the privacy policy
- analytics
- Vercel Web Analytics (cookieless)
- scheduling
- Cal.com
The legal list of subprocessors lives in the privacy policy and DPA.
Found something in Midkernel?
security@midkernel.com · we acknowledge within two business days and publish fixes in the changelog.
No SOC 2 or ISO 27001 report yet. What we do instead: this page, and the pinned provenance on every run. When a compliance report exists it will be linked here.
Does it need write access?
No. The GitHub app requests read access to code and metadata only. Continuous runs, when they ship, will comment on pull requests through a separate, optional permission.
Can I run it on a private repository?
Yes; that is the normal case. The sandbox sees the repository only for the duration of the run.
Can I run Midkernel in my own cloud?
No hosted private-cloud option. A self-hosted runner is how the platform is designed to run anywhere you like; that repository is not public yet.