Skip to content
Capstone Quarry
CoursesExploreSign in / Create account

Capstone Quarry — build it, prove it, keep it.

Explore certsPrivacyTermsAcceptable use
Legal

Terms of Service

The rules for using this platform. The sections on what verification does and does not prove, and on the sandbox and liability, matter more than the usual boilerplate — please read them.

Last updated 14 October 2026

What this service is

Capstone Quarry provides guided, hands-on cybersecurity capstone projects that you build in your own lab environment, together with a record of the work you verify along the way. It is educational material. It is not a certification body, and completing a capstone here does not award any vendor certification.

What a “verified” step actually means

When you paste command output and it matches the expected result, we record that a match occurred, hash the text, and timestamp it. That is the entire claim.

It is not proof that a command ran on real hardware, that your lab is configured correctly, or that the work is of professional quality. The check runs in your browser and a determined person could defeat it. In cloud mode the platform may issue the stamp you echo into your output and log a receipt that the stamp came back matched; a receipt records the stamp, not the machine. Do not represent a verification record as an audited or independently invigilated result, and do not rely on one when assessing someone else.

Sandbox and liability

Every capstone exercise runs in a sandbox you control and can rebuild: your own machines, virtual machines, isolated networks, or cloud accounts you pay for. Nothing in a course is pointed at a production, school, employer, customer or public system.

You bear every cost and consequence of what you run there: cloud charges and any overcharge, data loss, outages, misconfiguration, misuse of a tool or technique, and every implementation decision you make. Capstone Quarry, its operators and instructors are not liable for any cause, implementation, overcharge, misuse or consequence arising from the capstone work, inside or outside the sandbox. The Acceptable Use Policy says what you may and may never do with the techniques taught here.

Your lab, your responsibility

The exercises involve security tooling — scanners, exploitation frameworks and traffic capture. You agree to run them only against systems you own or have explicit written authorisation to test, on an isolated network. Running these tools against systems you do not have permission to test is illegal in most jurisdictions. You are solely responsible for what you point them at.

You are also responsible for the security of your own lab, and for not storing production or reused credentials in the platform.

Your account

You must provide an accurate email address, keep your credentials secure, and not share your account. Every account accepts the platform agreements when it is registered, before the platform can be used. You may delete your account at any time from the account page. We may suspend accounts that abuse the service, attack the platform, or use it to attack others.

Your content

The deliverables, notes and evidence records you create remain yours. You grant us only the permission needed to store and display them back to you and, where you have joined a team, to your teammates. We do not claim ownership and do not use your content to train models. Where you create a link to a copy of your export, you authorise us to show that frozen copy to whoever holds the link until it expires or you revoke it.

Availability and liability

The service is provided “as is”, without warranty. We do not guarantee uninterrupted availability, and we are not liable for loss of data, loss of progress, or any damage arising from your use of the exercises or tools described here. Export your portfolio if you need a durable copy.

Changes

These terms may change as the product does. Material changes are reflected in the date at the top of this page and in the version number of the agreement you accept in the app. A changed agreement is presented again at your next sign-in and must be accepted before use continues; the acceptance log records which version you agreed to and when.

See also Terms of Service, Acceptable Use Policy and Privacy Policy.