# Bitdata ObjectStack Applications > Bitdata builds governed, AI-native business applications on ObjectStack protocol 17. This website is available in Simplified Chinese and English. ## Primary pages - [中文概览](https://bitdata-ai-plugin-site-eta.vercel.app/zh): Bitdata product overview and ObjectStack-native application model. - [English overview](https://bitdata-ai-plugin-site-eta.vercel.app/en): English product overview. - [AiCRM 中文](https://bitdata-ai-plugin-site-eta.vercel.app/zh/aicrm): General-industry B2B lead-to-cash CRM. - [AiCRM English](https://bitdata-ai-plugin-site-eta.vercel.app/en/aicrm): English AiCRM product page. - [知识产权 CRM](https://bitdata-ai-plugin-site-eta.vercel.app/zh/crm): CRM for intellectual-property service organizations. - [IP CRM](https://bitdata-ai-plugin-site-eta.vercel.app/en/crm): English IP CRM product page. - [平台能力](https://bitdata-ai-plugin-site-eta.vercel.app/zh/platform): ObjectStack-native AI, metadata, data import, MCP, and agent capabilities. - [Platform capabilities](https://bitdata-ai-plugin-site-eta.vercel.app/en/platform): English platform capability page. ## Verified product facts - Applications are defined through ObjectStack protocol-17 metadata: objects, views, pages, actions, flows, permissions, dashboards, reports, and application navigation. - The IP CRM implements native CSV/XLSX import and governed channel-batch intake; ObjectStack connectors support REST, OpenAPI, and MCP integration. - ObjectStack MCP connectors can expose approved service operations without bypassing the application's authorization model. - The independently installed @bitdata/ai-plugin supplies in-product agent conversations, streaming responses, skills, tools, and approval-aware actions. - AiCRM covers the governed B2B lead-to-cash lifecycle. IP CRM covers acquisition, pricing, finance, contracts, professional matter delivery, deadlines, and IP assets. ## Deployment boundary Runtime credentials, tenant policies, approval staffing, production data validation, and external provider authority must be configured by the deploying organization. Product pages describe implemented source capabilities and do not claim a completed production deployment.