# FinClip Introduction
FinClip consists of three parts: Cloud, Client, and Developer Tools:

- The Cloud refers to the
FinClip Management Console(opens new window), which manages the entire lifecycle of Mini-Programs, including development and publishing; - The Client refers to the
FinClip Mini-Program SDK, representing mobile Apps or various smart devices that have integrated the FinClip Mini-Program SDK, providing them with the capability to run Mini-Programs; - Developer Tools are primarily used for writing, debugging, uploading, and previewing Mini-Program code.
# How Does the FinClip Mini-Program SDK Work?
The FinClip Mini-Program SDK provides a Security Sandbox and Host Environment capable of running Mini-Program business code:
- The
Security Sandboxis responsible for protecting the business applications within the Mini-Program, transmitting data in a secure and trusted environment to avoid interference and eavesdropping by third parties; - The
Host Environmentis responsible for executing the Mini-Program's JS business logic code and uses WebView to render and display the Mini-Program pages (Learn more).
# What is the FinClip Mini-Program Security Sandbox?
The FinClip Mini-Program SDK also serves as the Security Sandbox for Mini-Program execution. Within the Mini-Program's Host Environment, mobile or desktop applications need to interact with both the Logic Layer and the View Layer. These two layers cannot communicate directly and can only exchange data through the Host-App.

Because of this, FinClip can also be used to ensure the security and reliability of the Mini-Program Runtime:
- The FinClip Mini-Program SDK provides a closed, secure Runtime for the business code, effectively preventing risks such as interference from external code and data leakage. Hosts from third-party network platforms can only start the Runtime through the interfaces actively exposed by the SDK;
- The FinClip Mini-Program SDK can fully control the Runtime environment required by the business application and its necessary external communications, and can employ various mechanisms to ensure that network communications are not intercepted or interfered with;
In desktop and Android environments, we also use the following methods and means to ensure the security and reliability of the Mini-Program Runtime:
- The desktop version uses the
Chromium Embedded Frameworkbrowser kernel. The Runtime is completely isolated from the system browser, enabling effective data isolation and protection based on this kernel.
# iOS SDK Integration Guide
- Integration Guide
- Common APIs
- iOS SDK FAQ
- iOS SDK Update Log
# Others...
If you need to view related DEMO examples, you can check our repositories on Github (International) (opens new window) and Gitee (China) (opens new window).