> For the complete documentation index, see [llms.txt](https://roseon.gitbook.io/roseon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://roseon.gitbook.io/roseon/whitepaper/roseon-ecosystem/platform-architecture.md).

# Platform Architecture

**Roseon microservice architecture can be divided into four main groups:**

![](/files/-MX5VUYZGvoYVXjN_3lc)

**Management Tool**

Management functionalities act as the gateway to provide vendor-agnostic services to the Roseon Mobile Application or any future third-party web or mobile interface. The main functionalities include:

* User Management allows the system to manage user registration, role permissions, and groups
* Wallet Controller provides the core functionality of a wallet (ie. deposit and withdrawal)
* DeFi Controller offers term Savings feature
* Farming Controller offers Farming features
* Portfolio Management Controller create, monitor and rebalance your crypto portfolio
* NFT controller provides access to NFT asset

**Integration Service**

Roseon’s Integration Service acts as an aggregator or connector to external centralized and decentralized platforms via API or smart contracts.

**Business Intelligence & Analytics**  

Roseon will offer advanced analytics and dashboard reporting that collects on-chain and off-chain user and asset data to provide analysis, and reports on market opportunities, and data analysis to expand their user base.

**Custodial Services**

Roseon will offer clients access to secure, institutional-grade offline cold storage, the most reliable custody solution. Roseon will also work with world-class custodial services such as Coinbase and Primetrust to ensure the safety of funds. The Custodial Service secures any cryptocurrency assets, restricting access and ensuring the privacy of any digital asset in the storage. The service relies on other listening services such as Bitcoin Node, Ethereum Node, to communicate with the respective Blockchain.

The Custodial Service includes 5 core components:

* Wallet Service provides the functionality of a wallet, keeping track of and facilitating deposit and withdrawal.
* Secret Key Service secures all private keys.
* Transaction Queue holds pending high-value transactions waiting for admin approval. The Transaction Verification Dashboard shows all pending transactions in which the Admin can approve and sign the transaction using his private key.
* Listening Node is the gateway to Blockchain.
* Multi-signature smart contract for keeping funds safe.

![](https://lh5.googleusercontent.com/EqZ_5NfWRhC-iNCc4zwzErQToYIu0hApFrV8moyFX8qSZ6a5IKsNG3kAjlTr9vFdsiAVqRdSwJbLsPI4lZKr47LkM6gSuyhAy7xsMw1ALydHu5ypDSf0PQOj7PFStnb_-IzoIFms)

\
The service provides secure storage of cryptocurrency assets by using a Multi-Signature smart contract. The contract treats two following type of transaction differently

* Low-value transactions can be passed through immediately as long as the sender is the Wallet Service
* High-value transactions are queued at Transaction Queue and waiting for approval from Admin. Upon approval, Admin initiates one signature. Together with the signature generated from Wallet Service, these two signatures can unlock high-value transactions. Checking the validity of these two signatures is the responsibility of this Multi-signature smart contract.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://roseon.gitbook.io/roseon/whitepaper/roseon-ecosystem/platform-architecture.md?ask=<question>
```

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.