TERMS

What you are buying,
and what it does not promise.

Alongside is operated by Alongside Software, LLC. Connect a repository or a URL, spend a credit, get a report. These terms cover what that report is, what you have to be entitled to hand us, and where the money goes. Last reviewed 7 August 2026.

CREDITS

One credit, one audit, one project.

A credit is consumed when the run is created rather than when it finishes, because one credit that could queue ten runs is not a credit.

A run that produces nothing gives the credit back

In full, automatically. A run that dies partway and still found things is delivered as what it found, and you keep the report.

Credits are shared across your team

Seats are unlimited. Owners buy, members spend, viewers read. Nobody without the owner role can change what you pay.

Subscription credits and pack credits are not the same

Automated re-tests reserve subscription credits a month ahead; packs and evergreen credits cannot cover them. The screen that schedules one says so before you commit.

Prices are what the site says on the day you buy

A change to the list price does not reach a subscription until its next renewal.

WHAT THE REPORT IS

Measurements and judgments about one commit.

Some of a report is counted — lines, dependencies, advisories, test results, contrast ratios. The rest is a model's judgment, marked apart from the counted half so you can tell which you are reading.

It is not a warranty that your code is secure

An audit that finds nothing is an audit that found nothing, and that is all it is. Nobody can read a codebase and certify the absence of every defect, and a report claiming to would be worth less than one that does not.

It is not a certification and not legal advice

Where a finding touches a regulation it comes with the evidence, described in terms of your code, so you can hand it to whoever asked. That is not the same as us telling you whether you comply.

A finding can be wrong

Every one carries a file, a line and a commit for exactly this reason. If one is wrong you can prove it, and we would rather you did than took our word for it.

It describes the code at one revision

Pinned to the commit audited. That is what makes it worth reading a month later, and what stops it being read as a statement about your code today.

YOUR SIDE

You have to be entitled to hand us what you hand us.

We cannot check any of this from where we stand, so it sits with you. Getting it wrong is the one way this service causes a problem for somebody who never agreed to anything.

The repository is yours to share

Yours, your employer's, or one you have permission to have read. The token you create is read-only and one repository wide, and you can revoke it whenever you like.

The URL is yours to point us at

A design audit opens a live site and clicks around it. Give us an address you control. Pointing us at somebody else's application is using us to probe it, and it is not permitted.

The test login is a test login

If a flow behind sign-in shows real people's data, that decision and its lawful basis are yours. Use an account with as little in it as the audit needs.

You keep everything you already own

Your code stays yours. The report is yours. We do not sell either, and we do not use your source to train anything of ours.

AVAILABILITY

No uptime figure, because we have not measured one.

Stating a percentage we have not calculated would be the first false sentence on the site. What we will say is what happens when a run does not work.

A failed run costs you nothing

The credit comes back in full and the machine is destroyed regardless of how the run ended.

A partial run is labeled partial

You get what was confirmed before it stopped, and the report says where it stopped rather than presenting a short list as a complete one.

We can suspend an account that is attacking someone

Repeated audits pointed at applications you do not control, or use of the sandbox to reach anything else, ends the account.

We are not liable for what the audit does or does not find

To the fullest extent Texas law allows, we are not liable for any loss arising from using Alongside — including a defect the audit missed, a finding it got wrong, or anything you changed because of one. The audit is a second opinion, not a warranty. Some liability cannot be excluded by law and we do not try to exclude it.

Texas law governs these terms

Alongside Software, LLC is the contracting entity and Texas is where an agreement with it is governed and where a dispute would be heard.

You can leave at any time

Cancel a subscription and it runs to the end of the period you paid for. Closing the account is by email — the privacy page says what happens to your data.

Ask before you agree, not after.

hello@alongside.dev

What happens to your code is on the security page; what we hold about you is on the privacy page.