StackCircuit365
Legal

Terms, privacy, and attributions.

Effective September 2, 2026. StackCircuit365 is prerelease software. These terms and this policy cover the current 0.5.0 prerelease and will be updated as the product reaches its public launch. Questions can go to hello@stackcircuit.dev.

Terms of Service

By installing the stackcircuit365 package, connecting it to your GitHub and Vercel projects, or using the software in any form, you agree to the terms below.

1.0

The software

StackCircuit365 is free, open-source software published on npm as stackcircuit365. You run it yourself, on your own infrastructure. It monitors deployments from GitHub to Vercel, detects release regressions in production, recommends or performs rollbacks under rules you configure, and produces incident reports. It is offered under the MIT license and has no paid tiers.

1.5

Open source and license

The source code is released under the MIT license and is available on npm and GitHub. You are free to use, modify, and self-host it, including for commercial projects, subject to the license text that ships with the package. The MIT license governs the code itself; the operational terms on this page apply to how you run it against production systems.

2.0

Your responsibilities

You are responsible for the code you deploy, for the recovery mode you select, and for reviewing any rollback recommendation before you approve it. Auto-Recover is off by default and takes effect only after you enable it and accept the risks described in the dashboard.

3.0

Access and permissions

StackCircuit365 requests the minimum GitHub permissions needed to do its job. It starts with read access to repository metadata and contents. Any write permission, such as creating issues or draft pull requests, is opt in and can be revoked at any time from GitHub.

4.0

Automated actions

A deterministic policy engine governs every rollback and every write. The service will not automatically touch database migrations, authentication, authorization, billing, secrets, environment variables, or any change it cannot verify as safe. In those cases it stops and alerts you.

5.0

Prerelease software, provided as is

The prerelease is provided without warranties of any kind. We do our best to make recovery safe and correct, but you should not rely on it as the only safeguard for a production system. StackCircuit365 is not liable for indirect or consequential damages arising from use of the prerelease.

6.0

Free forever, with fair use

StackCircuit365 is free to use and has no paid tiers. Core release monitoring, incident reports, rollback recommendations, and policy-controlled recovery stay free. Reasonable fair-use limits keep it sustainable, such as one repository, one Vercel project, one production URL, standard health checks, a limited incident history, and a capped number of repair attempts. These limits may be adjusted over time, but the product stays free.

7.0

Changes and termination

You can disconnect StackCircuit365 from GitHub and Vercel at any time. We may update these terms as the product matures and will post the effective date at the top of this page.

Privacy Policy

StackCircuit365 runs on your infrastructure, not ours. When you self-host the open-source package, we never receive your deployments, health data, or secrets. We do not sell data, and there is nothing for us to sell.

1.0

Self-hosted by default

You run the stackcircuit365 package yourself. Everything it works with, including Vercel deployment events, GitHub commit metadata, health-check results, your alert settings, and any tokens you provide, stays on your own machine or server. It is sent only to the services you point it at, using credentials you control. The authors of StackCircuit365 receive none of it.

2.0

What the software touches

To do its job on your infrastructure it reads deployment events from Vercel, commit metadata and changed file names from GitHub with read-only access by default, and health responses from your production URL. It never clones your repository or reads source beyond the changed files needed to explain an incident. Webhook events are signature verified and stored in your own datastore so every automated action can be traced.

3.0

This website

stackcircuit.dev is a static marketing site hosted on GitHub Pages. It has no accounts and no login, and it sets no tracking cookies. If you email us at hello@stackcircuit.dev, we keep that message so we can reply.

4.0

Third parties and your credentials

StackCircuit365 talks to the services you connect, such as GitHub and Vercel, and optionally Slack or an email provider like Resend, using tokens you supply and store yourself. Those services process data under their own terms. When you self-host, we are not a processor of your production data.

5.0

A hosted version, later

If a managed hosted instance is offered in the future, it will carry its own clearly posted privacy terms and its own data handling, and using it will be optional. This policy describes the open-source software you run today.

6.0

Security

Secrets and credentials never leave your infrastructure. Every rollback and write is gated by the deterministic policy engine and the recovery mode you choose, and read-only monitoring needs no write access at all.

Attributions

StackCircuit365 is designed and built by its two co-founders.

Rahul Awasthi

Lead Developer and Architect

Detection and recovery engine, policy engine, and platform architecture.

Pritam Avuthu

Lead Product Designer

Product design, incident reporting experience, and the StackCircuit365 brand.

StackCircuit365 is built with Next.js, TypeScript, and Tailwind CSS. Product and company names referenced on this site, including GitHub and Vercel, are trademarks of their respective owners and are used here for identification only.