Documentation Sites and Endpoints
ANKASecure publishes its documentation as several sites rather than one. They are built from a single source tree and differ only in which pages each one contains: each site is a superset of the ones below it, so a reader entitled to one can read everything on the sites beneath it.
This page describes the sites that are open to you, what each is for, and how to ask for access to the one that is not.
1. Open to everyone
| Site | Address | What it is for |
|---|---|---|
| Documentation | docs.ankatech.co | The public documentation: API reference, SDK and CLI guides, quickstarts, algorithm catalogue, compliance overviews and migration guides |
| Developer Hub | apidocs.ankatech.co | The interactive API reference, generated from the API definition — request panels, per-operation schemas and end-to-end recipes |
| Downloads | bootstrap.ankatech.co | The installer media and admin bundle the installation procedure fetches |
The public documentation is also readable by an AI assistant over MCP. The public endpoint is announced on the public documentation site itself; there is nothing to request and no credential to hold.
2. Open to customers, on request
| Site | Address | What it is for |
|---|---|---|
| Customer Documentation | customers.ankatech.co | Everything on the public site, plus what an organisation that runs ANKASecure needs to plan, install, upgrade, operate, integrate and certify its installation: system requirements and sizing, the installation and upgrade procedures, day-two operations runbooks, the integration guides for each external system, and the integration certification matrix |
Once you are in, start at the Customer Guide, at the top of that site's navigation. The same pages can be queried in natural language from inside Claude: the Customer Guide explains how to connect the documentation assistant, which answers from the pages of this site and from nothing above it.
Requesting access
Access is granted in one of two ways, and sign-in uses a one-time PIN sent to the address in both:
- Per person, by work email address. Each address is added individually.
-
Per organisation, by email domain. Everybody who receives mail at your organisation's domain is admitted, without naming each person. Ask for this when the people who operate the installation change often; a domain grant admits anyone at the domain, so the organisation, not ANKATech, decides who that is.
-
Ask your ANKATech contact, or write to [email protected], naming either the people who need access and the work address of each, or your organisation's email domain.
- Open customers.ankatech.co, enter your work address, and confirm the PIN it sends you.
There is no shared password and nothing to store. Tell your ANKATech contact when someone leaves: an address granted by name is removed by name, and a person covered by a domain grant is excluded by address.
3. Open to partners, on request
| Site | Address | What it is for |
|---|---|---|
| Partner Documentation | partners.ankatech.co | Everything on the customer site, plus the material ANKATech approves for partner sales, pre-sales and delivery teams: positioning and competitive material, use cases by industry, demo scripts, the delivery methodology and the partner programme |
Once you are in, start at the Partner Guide, at the top of that site's navigation. A partner admitted here is also admitted to the customer site.
Requesting access
Access is granted per person, by email address. Sign-in uses a one-time PIN sent to that address; there is no shared password, and nothing to store.
- Ask your ANKATech contact, or write to [email protected], naming the people who need access and the email address each should be granted on.
- Each address is added individually. A grant is to one mailbox, not to a domain, so every person is named.
- Open partners.ankatech.co, enter that address, and confirm the PIN it sends you.
Access is removed the same way it is granted — per address, on request — so tell your ANKATech contact when someone leaves the engagement.
4. ANKATech-internal
Two further sites exist and are not open to customers or partners. Each is a superset of the partner site:
- One for all ANKATech employees, reached through ANKATech's corporate identity provider. It adds the material about how ANKATech runs its own service and its own platforms: its SaaS topology, its CI/CD, its release and documentation publication procedures.
- One for a named list of individuals. It adds internal architecture designs, security audit findings, examination material and credential references.
Their addresses are not published here, and this is deliberate: naming an endpoint nobody outside ANKATech can use adds nothing for the reader and adds a target for everyone else. If you are an ANKATech employee, both are listed in the internal documentation-access runbook.
5. Why a link sometimes goes nowhere
The sites are built from one source tree, so a page you can read may link to a page your site does not contain. That link renders as an inert stub rather than a broken link or a login prompt: the text stays, and it does not navigate.
A stub is not an error and not a permissions failure. It means the page it points at belongs to a site above yours. If you believe you should have it, the classification is recorded — every page's tier, and the criteria behind it, is decided by the rules in ANKATech's content-classification governance, and your ANKATech contact can have a specific page reviewed.