Keystone Computer
License Agreement
This is the Alexandria Software License Agreement referred to by every license file Keystone issues. It governs your use of the software itself. If you also bought hardware from us, the Terms cover that sale, and this agreement covers what runs on it.
Last updated 26 July 2026
1.What this agreement is
This agreement is between you, the organization or person named as licensee, and Keystone Context Computer, Inc., trading as Keystone Computer (“Keystone”, “we”, “us”). It applies when you install, activate, or use the Alexandria software, whether or not you also bought a server from us.
Where you have signed a separate written license or purchase agreement with us, that document governs and this one fills the gaps. Where a term conflicts, the signed document wins.
2.The license we grant
Alexandria is licensed, not sold. Subject to this agreement and to payment of any fees due, we grant you a non-exclusive, non-transferable, revocable license to install and run the software for your own internal business purposes, on the hardware and for the number of seats your license covers, for as long as that license is in effect.
The license is personal to the licensee. It does not travel to another company if your business is sold, and it cannot be lent, resold, or shared with another organization, except that your own affiliates and contractors may use it on your behalf while bound by these terms.
We retain all intellectual property rights in the software and its documentation. You get the right to run it. Nothing here transfers ownership of any of it.
3.Your license file and key
We provision Alexandria with a license file. It is signed by Keystone, so the software can confirm it was issued by us and has not been altered, and it identifies you as the licensee. It may also carry a Keystone key for metered model access.
- Treat it as a credential, not a certificate
- A license file is not a receipt or a brochure. Where it carries a key, that key is live and spends against your account from the moment it is issued. Anyone who obtains the file can use it until it is revoked, so handle it the way you would handle a password.
- Revocation is the enforcement mechanism
- A license does not police itself and does not need to phone home for permission to run. If entitlement ends, whether through non-payment, a breach, or a file you tell us has leaked, we revoke the key, and metered model access stops working. Tell us promptly if a license file is exposed and we will reissue it.
- Keep it out of shared places
- Do not commit a license file to a repository, paste it into a ticket, or circulate it by email. Where the software stores it for you, it belongs in the operating system's credential store, not in the vault.
4.Metered model usage
Where your license includes a Keystone key, model usage is metered against that key and billed as part of the product. The key is a Keystone credential: it is not a model provider's key, and it does not entitle you to raw access to any provider's models or endpoints. What you are licensed to use is Alexandria.
Usage is subject to the budget and rate limits attached to your key. We may cap, pause, or revoke a key that exceeds its budget, appears compromised, or is being used abusively, and we will tell you when we do.
Requests you route through the Keystone gateway reach a third-party model provider: today, Anthropic. That provider's usage policies apply to what you send, in addition to this agreement. By using metered model access you agree to comply with Anthropic's Usage Policy as it stands from time to time, and to be responsible for the content your organization and its agents submit. If we change or add providers, the policies of the provider actually serving your requests apply, and we will say so here.
You can avoid this entirely by running open-weight models on the server's own GPUs. That path involves no key, no gateway, and no third-party provider.
5.What you may not do
You agree not to:
- sublicense, resell, rent, or offer the software to third parties as a service;
- reverse engineer, decompile, or disassemble it, except to the extent applicable law expressly permits despite this restriction;
- remove, obscure, or alter any proprietary notice, license file, or brand mark;
- circumvent licensing, metering, seat, or entitlement controls, or share license credentials outside your organization;
- use the software, or its output, to develop a competing product;
- use it unlawfully, or in the ways ruled out by the acceptable-use section of our Terms.
6.Your content stays yours
You own everything your organization puts into Alexandria and everything its agents produce. We claim no ownership of it and take no license to it. We do not use your content to train models.
The software is built so that we do not need access to your vault, and in ordinary operation we do not receive one. The Privacy notice sets out the narrow cases where information does leave your machine, and what goes where.
7.What the output is, and is not
Alexandria is an AI system. Its output is generated by language models, which are probabilistic: it can be wrong, incomplete, out of date, or confidently mistaken, and it can misread the material it is given. Factual assertions in output should not be relied on without checking them.
Output is not legal, financial, medical, tax, or other professional advice. Keep a human in the loop for consequential decisions, and review output before you rely on it, publish it, or act on it.
Where you put Alexandria in front of customers, clients, or correspondents outside your organization, you are responsible for making clear that they are dealing with an AI system, and for any disclosure your own regulators require.
You remain responsible for decisions your organization makes, whether or not an agent contributed to them.
8.Updates and changes
We release updates from time to time. Whether you receive them, and for how long, depends on your license and any support arrangement in your order documentation. Updates are covered by this agreement unless we ship different terms with them.
Features change as the product develops. Where a change would materially reduce functionality you rely on, we will give reasonable notice. We may also update this agreement; the current version is always at this address, with the date it was last updated, and material changes take effect at your next renewal.
9.Suspension and termination
This license runs until it ends: when its term expires, when either of us terminates for a material breach the other has not cured within thirty days of written notice, or when you stop using the software.
On termination you stop using the software and destroy or return the license files we issued. Your vault is yours and stays yours: it is plain files on your own hardware, and nothing about termination takes it away, locks it, or makes it unreadable. Hardware you bought remains yours.
Sections that by their nature should survive do so on termination: ownership, restrictions, your content, disclaimers, liability, and governing law.
10.Warranty and liability
We warrant that the software will perform substantially as documented during any warranty period stated in your order documentation. Except for that, and to the fullest extent the law allows, the software is provided “as is”, and we disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that output will be accurate or that operation will be uninterrupted or error-free.
To the fullest extent permitted by law, neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, business, or data. Each party's total liability arising out of or relating to this agreement is capped at the amounts you paid to Keystone for the license in the twelve months before the event giving rise to the claim.
Nothing here limits liability for fraud, fraudulent misrepresentation, death or personal injury caused by negligence, or anything else that cannot lawfully be limited. Because some jurisdictions do not allow certain exclusions, parts of this section may not apply to you.
11.Governing law
This agreement is governed by the laws of the State of New York, without regard to its conflict-of-laws rules, and the parties submit to the exclusive jurisdiction of the state and federal courts sitting in New York County, New York. You agree to comply with applicable export control and sanctions laws.
If a provision is held unenforceable, the rest stays in force. You may not assign this agreement without our consent.
12.Contact
Questions about this agreement, license files, and reissues: hello@keystone.computer, or by post to Keystone Context Computer, Inc., 250 W 55th St, New York, NY 10019, United States.