Contact

Let us start with your organisation, not our product.

The first conversation is not a product pitch. We map together where decisions are made in your organisation and where the evidence sits.

What happens after you ask for a demo

The most uncomfortable thing for an enterprise buyer is not knowing what follows the form. Our process is short and every step is optional; you can stop wherever you like.

  1. A short introductory call. About half an hour. We do not present the product; we map together where change and data access decisions are made in your organisation today and where the evidence sits. If you complete the self assessment beforehand, we start from there.
  2. A walkthrough on your own scenario. Rather than a generic tour, we run the situation you described end to end in the product: from opening a request to the sealed evidence file. You can bring your own script.
  3. Technical and security review. Your teams examine the architecture, the deployment model and the security controls. The security page and the control mapping are the starting point, and bringing your own control list is the most productive route. We say plainly which items have no answer.
  4. An optional pilot. If you want one, we install against a single production server. We recommend keeping the scope narrow: whether audit questions about that server can be answered within minutes a quarter later is a measurable outcome.

An honest note

We are an early stage product. We have no reference customer list, no independent certification and no analyst report, and we do not claim otherwise. In return we are completely open to your own technical and security review. What working with us at this stage buys you is real influence over the roadmap.

Reach us directly

Call us during business hours, or write and we will come back to you within one business day.

General enquiries
info@sqlchangeguard.com

If you complete the six question self assessment beforehand, the conversation starts from your own situation.

Write to us

A short note is enough. Telling us which databases you run and the question that brought you here helps us answer more precisely.

Your message is delivered from our own server and reaches us only. It is not passed to any third party.

About us

What we are, and what we are not yet, stated as it is

Why This Product

The enterprise IT stack matured around the application layer. Source repository, code review, delivery pipeline, release tag: on the application side the answer to what went to production sits in one place and nobody argues about it.

The database layer never reached that maturity, and the reason is not technical: work that touches the database does not flow through a single channel. A schema change goes through the pipeline; a data correction does not. Nor does a permission change, nor an emergency fix at night. A request to extract production data for an audit was never any pipeline's business. In most organisations the process covers exactly one of the roads into production and the rest proceed unrecorded.

SQL Change Guard was written for that gap. It does not replace your existing tools; it answers the question they leave open: was the text that ran the text that was approved, and who reached production data, on what stated basis?

The Decisions That Shape the Product

These are not marketing lines but engineering decisions with real consequences that we live with.

It runs inside your network

We do not offer a cloud service. Your scripts, query results and records never come to us; they leave your environment only through connections you open and recipients you approve. This is the harder distribution model for us, since installation and release management live on the customer side. We still think it is the right call: for a product that touches a production database, where the data sits should not be up for discussion.

SQL is parsed with a real grammar

Keyword matching is fast and easy, and it misleads: whether a statement is unqualified, which object it touches and what type it is can only be established reliably by analysing it against the grammar of the language. Maintaining three separate parsers for three databases is expensive; assuming a shared syntax produces silent errors.

We write down our limits

What the product cannot do sits under its own heading on the security page. We cannot stop someone with full access to the server from doing anything at all; what the ledger gives is detectability rather than immutability. We say this in a sales meeting before being asked, because saying it when asked is too late.

We do not fabricate proof

You will not find a customer logo, a testimonial, a certification badge or an analyst quote on this site. We have none of them and we do not pretend otherwise. Instead we put up real product screens, real flows and verifiable technical detail.

What Stage We Are At

We are an early stage product. We say so up front because it affects your evaluation. In practice that means: