Terms of Service

Envgrid is operated by GULIN BOGDAN P.F.A., a sole trader registered in Romania. Full registration details are at the foot of this page. “We” and “us” mean that business; “you” means the person or company using Envgrid.

Using Envgrid means accepting these terms. If you are agreeing on behalf of a company, you confirm you are allowed to bind it.

Envgrid is a read-only dashboard showing which commit is deployed in each of your environments, what would ship if you deployed now, and what shipped previously.

It never triggers, changes or stops a deployment, and it holds no credentials for your runtime infrastructure. It learns what is deployed only because your pipeline tells it, through a webhook you configure, or because someone on your team records it by hand.

That means Envgrid reports claims, not facts. A webhook proves that somebody holding your environment’s secret asserted that a commit reached that environment at that time. It does not prove the deployment succeeded, that it is still running, or that every instance is on it. Envgrid shows the age of every claim so you can judge it, but you must not treat the dashboard as verification that a system is in a particular state.

An organization is the unit that holds services, history and billing. Membership is all or nothing: anyone you invite can read every service, environment, deployment, commit message, author name and linked ticket in that organization. There are no per-service permissions.

Commit messages from private repositories routinely say more than people expect. Inviting somebody hands over the whole history, not a slice of it, and doing so is your decision to make.

• You are responsible for keeping your login credentials secure and for what people you invite do with their access.
• Owners can add and remove members, change roles, connect and disconnect providers, and delete the organization.
• Every organization must keep at least one owner.
• Webhook secrets let anyone holding them write deployment records. Treat them as credentials, reveal them only to people who need them, and rotate them from Settings if one leaks.

Envgrid reads from GitHub, GitLab and Jira when you connect them. It only ever reads, and only what the connection you granted permits.

You confirm you are entitled to connect those accounts and to have their contents shown to everyone in your organization. You can disconnect at any time from Settings → Connections; doing so stops further reads and leaves already-stored history in place until you delete it.

• Do not use Envgrid unlawfully, or to store or transmit anything unlawful.
• Do not attempt to access another organization's data, probe for weaknesses, or work around the limits of your plan.
• Do not resell Envgrid or present it as your own product.
• Do not automate requests at a volume that degrades the service for others.

If you find a security problem, please report it to support@envgrid.dev rather than exploring it. We will not pursue anyone who reports a genuine issue in good faith and gives us a reasonable chance to fix it.

Plans and their service limits are listed on the pricing section. Prices are shown excluding tax; the tax applicable where you are is added at checkout and shown before you pay.

Payments are processed by Paddle, who act as the merchant of record. Your contract of sale for the payment itself is with Paddle, their buyer terms apply to the transaction, and their name appears on your statement. We never see or store your card details.

Subscriptions renew monthly until cancelled. Refunds and cancellation are covered by our Refund Policy, which gives you 14 days from your first payment to change your mind.

We may change prices. Existing subscribers will be told before a change affects them and can cancel rather than accept it.

We work to keep Envgrid available and correct, but it is provided as is, without a guaranteed uptime level. There is no service level agreement on any plan today, and saying otherwise would be a promise we have no mechanism to keep.

Envgrid also depends on systems we do not control — GitHub, GitLab, Jira, our hosting and database providers. When one of those is unavailable, parts of Envgrid will be too. Where that happens, Envgrid is designed to say it could not reach a provider rather than to report the absence of an answer as an answer.

To the extent the law allows, our total liability to you for any claim is limited to what you paid us in the twelve months before it arose, and we are not liable for lost profits, lost data, or losses arising from a deployment decision made while looking at Envgrid. Nothing here limits liability that cannot lawfully be limited.

You can stop using Envgrid whenever you like: cancel your subscription from Settings → Billing, and delete your organization or your account from Settings. Deleting an organization permanently removes its services, deployment history and changelogs.

We may suspend or close an account that breaches these terms, that is being used unlawfully, or whose payments have failed and not been resolved. Except where something urgent or unlawful is happening, we will contact you first and give you a chance to put it right.

We may update these terms as the product changes. The date at the top shows when they last changed, and material changes will be notified by email to organization owners before taking effect. Continuing to use Envgrid after that means accepting the new terms.

These terms are governed by Romanian law, and the courts of Romania have jurisdiction. If you are a consumer, this does not deprive you of the protection of the mandatory law of the country you live in.

Before anything formal, please write to support@envgrid.dev. Most problems are a misunderstanding, and almost all of them are cheaper to fix by email.