# Getting Started ### Welcome to BTOS **Byzanlink Tokenisation OS or BTOS**, is Byzanlink’s tokenisation infrastructure for institutional financial products. It is built to help issuers bring funds, private credit, real estate, commodities, and other structured products onchain through a controlled, modular, and lifecycle-ready operating model. BTOS is designed for institutions that need more than token issuance. It supports the broader product lifecycle across setup, compliance controls, investor access, subscription and redemption workflows, servicing, reporting, and ongoing operational management. #### Overview BTOS is a product stack that combines tokenisation workflows, compliance controls, investor access, servicing applications, and operational visibility into one institutional platform. At a high level, BTOS includes: * **Investor App** for investor access and interaction with tokenised offerings * **Servicing App** for issuer-side project setup and operational management * **BTOS API Engine** for embedding tokenisation workflows into existing systems * **BTOS White-Label Solution** for branded institutional deployment * **Lifecycle and Compliance Management** for controlled product operations * **Reporting and Operational Visibility** for monitoring holdings, transactions, and lifecycle activity BTOS is designed to support structured and permissioned financial products where lifecycle events, access rules, and operating controls matter as much as issuance itself. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.byzanlink.com/byzanlink-tokenisation-os/getting-started.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.