# ObjectOS

> ObjectOS is the target format and runtime for AI-written enterprise software: an AI agent generates the application as governed metadata, a human reviews it as a small diff, and the runtime keeps every action inside permissions, approval, and audit.

Built for a world where AI writes the code. ObjectStack is the open protocol (Apache 2.0) for defining business objects, relations, permissions, flows, APIs, and AI tools as portable metadata in your own repository; ObjectOS is the self-hosted runtime that executes that metadata and enforces governance. Teams model business objects, generate application structure from natural language, connect existing systems without migration, and let AI agents operate inside enterprise permission boundaries. In the open-source edition, you bring your own AI: ObjectOS exposes objects, queries, and business actions through MCP for clients such as Claude, Cursor, or a local model, while metadata is authored as source files and reviewed as a diff. The in-app AI Build (Studio) and Ask (data console) assistants ship in the Cloud and Enterprise editions.

## Primary Pages

- [Home](https://www.objectos.ai/en/): Governed runtime for AI-written business applications.
- [Product tour](https://www.objectos.ai/en/product-tour/): See how ObjectOS turns a business request into reviewable ObjectStack metadata, then runs the app with permissions, approvals, audit, APIs, UI, and AI tools.
- [Platform](https://www.objectos.ai/en/platform/): One governed runtime supplies the database, APIs, screens, automation, approvals, permissions, and analytics that every AI-written business application needs.
- [AI Build & Ask](https://www.objectos.ai/en/ai/): AI Build turns a described change into reviewable metadata. AI Ask answers questions over live business data inside user permissions. Open source brings your own agent via MCP.
- [Tools & MCP](https://www.objectos.ai/en/mcp/): The @objectstack/mcp server turns objects, queries, and actions into policy-checked tools for Claude, Cursor, or any MCP client — with permissions enforced on every call.
- [Permissions & security](https://www.objectos.ai/en/permissions/): Role-based, row-level, and field-level access control with a permission matrix editor and an audit log viewer, record sharing, and tenant isolation — enforced on people and AI agents alike.
- [Data modeling](https://www.objectos.ai/en/data-modeling/): Objects, relationships, validations, and formulas become tables, migrations, a query language, and REST APIs — with an object designer, an ER diagram, and datasource sync that federates existing databases in place.
- [App interfaces](https://www.objectos.ai/en/app-ui/): Forms, views, and dashboards render straight from metadata — shaped by each user’s permissions, updated in real time, and fine-tuned in a live-preview view designer with column inspectors and filter builders.
- [Process automation](https://www.objectos.ai/en/automation/): Multi-step flows with durable pause and resume, a visual flow canvas with 16+ node types, run history with test triggers, three trigger types, background jobs, and outbox-backed webhook delivery.
- [Approvals](https://www.objectos.ai/en/approvals/): Multi-step approvals with user, role, team, and hierarchy resolution, a three-tab approvals inbox, escalation, and record locking — the same queue that gates AI-written structural changes before they ship.
- [Analytics & reporting](https://www.objectos.ai/en/analytics/): Aggregations, time series, funnels, and dashboards over the same governed objects the app runs on — with a widget-based dashboard designer and a band-based report designer, permission-aware by construction.
- [Trust center](https://www.objectos.ai/en/trust-center/): Review the ObjectOS trust model: data residency, self-hosted deployment, identity, permissions, approvals, audit logs, AI tool boundaries, and enterprise security review materials.
- [Templates](https://www.objectos.ai/en/templates/): Start from reviewable ObjectStack templates for helpdesk, contracts, procurement, CRM, manufacturing, and employee service workflows instead of asking AI to generate a full app codebase.
- [Agent developer](https://www.objectos.ai/en/agent-developer/): Give your coding agent the rules, files, metadata patterns, and review checklist it needs to generate ObjectStack applications correctly and keep humans in control.
- [Reference stories](https://www.objectos.ai/en/customer-stories/): Explore realistic ObjectOS reference deployments for support, procurement, CRM, manufacturing, and internal service without pretending early examples are public customer case studies.
- [Security](https://www.objectos.ai/en/security/): Data residency, permissions, approvals, audit logs, and self-hosted deployment boundaries.
- [Pricing](https://www.objectos.ai/en/pricing/): Plans for open-source, cloud, and enterprise ObjectOS adoption.
- [Articles](https://www.objectos.ai/en/blog/): Practical writing on AI-native software, enterprise AI agents, integration, modernization, and governance.
- [Documentation](https://docs.objectos.ai/): Product and developer documentation.

## Topic Cluster Pages

- [AI-Native App Platform](https://www.objectos.ai/en/ai-native-app-platform/): Learn what an AI-native app platform is, how it differs from low-code, and how ObjectOS connects business objects, permissions, workflows, APIs, and AI agents.
- [Legacy System Modernization with AI](https://www.objectos.ai/en/legacy-system-modernization/): A practical guide to modernizing legacy business systems with AI by connecting existing databases, modeling business objects, and avoiding risky migrations.
- [Self-Hosted AI for Enterprise Applications](https://www.objectos.ai/en/self-hosted-ai/): Understand when enterprise AI should be self-hosted, which runtime components matter most, and how permissions, approvals, tools, and audit logs stay under control.
- [CRM and Case Management AI](https://www.objectos.ai/en/crm-case-management-ai/): See how AI can understand customers, opportunities, cases, and service workflows when CRM and case management data are modeled as governed business objects.
- [Manufacturing AI on Legacy Systems](https://www.objectos.ai/en/manufacturing-ai/): A practical manufacturing AI guide for connecting ERP, MES, work orders, reports, and operational data without replacing the systems that already run production.
- [AI-native 应用平台](https://www.objectos.ai/zh-Hans/ai-native-app-platform/): 了解 AI-native 应用平台 如何连接现有业务系统、建模业务对象，并让 AI 在权限、审批和审计边界内工作。
- [用 AI 做遗留系统现代化](https://www.objectos.ai/zh-Hans/legacy-system-modernization/): 了解 用 AI 做遗留系统现代化 如何连接现有业务系统、建模业务对象，并让 AI 在权限、审批和审计边界内工作。
- [企业应用的自托管 AI](https://www.objectos.ai/zh-Hans/self-hosted-ai/): 了解 企业应用的自托管 AI 如何连接现有业务系统、建模业务对象，并让 AI 在权限、审批和审计边界内工作。
- [CRM 与案件管理 AI](https://www.objectos.ai/zh-Hans/crm-case-management-ai/): 了解 CRM 与案件管理 AI 如何连接现有业务系统、建模业务对象，并让 AI 在权限、审批和审计边界内工作。
- [制造业 AI 与老系统连接](https://www.objectos.ai/zh-Hans/manufacturing-ai/): 了解 制造业 AI 与老系统连接 如何连接现有业务系统、建模业务对象，并让 AI 在权限、审批和审计边界内工作。
- [AI-native 應用平臺](https://www.objectos.ai/zh-Hant/ai-native-app-platform/): 瞭解 AI-native 應用平臺 如何連線現有業務系統、建模業務物件，並讓 AI 在許可權、審批和審計邊界內工作。
- [用 AI 做遺留系統現代化](https://www.objectos.ai/zh-Hant/legacy-system-modernization/): 瞭解 用 AI 做遺留系統現代化 如何連線現有業務系統、建模業務物件，並讓 AI 在許可權、審批和審計邊界內工作。
- [企業應用的自託管 AI](https://www.objectos.ai/zh-Hant/self-hosted-ai/): 瞭解 企業應用的自託管 AI 如何連線現有業務系統、建模業務物件，並讓 AI 在許可權、審批和審計邊界內工作。
- [CRM 與案件管理 AI](https://www.objectos.ai/zh-Hant/crm-case-management-ai/): 瞭解 CRM 與案件管理 AI 如何連線現有業務系統、建模業務物件，並讓 AI 在許可權、審批和審計邊界內工作。
- [製造業 AI 與老系統連線](https://www.objectos.ai/zh-Hant/manufacturing-ai/): 瞭解 製造業 AI 與老系統連線 如何連線現有業務系統、建模業務物件，並讓 AI 在許可權、審批和審計邊界內工作。
- [AI-native アプリプラットフォーム](https://www.objectos.ai/ja/ai-native-app-platform/): AI-native アプリプラットフォーム が既存システム、ビジネスオブジェクト、権限、ワークフロー、AI エージェントをどのようにつなぐかを解説します。
- [AI によるレガシーシステム近代化](https://www.objectos.ai/ja/legacy-system-modernization/): AI によるレガシーシステム近代化 が既存システム、ビジネスオブジェクト、権限、ワークフロー、AI エージェントをどのようにつなぐかを解説します。
- [企業アプリケーション向けセルフホスト AI](https://www.objectos.ai/ja/self-hosted-ai/): 企業アプリケーション向けセルフホスト AI が既存システム、ビジネスオブジェクト、権限、ワークフロー、AI エージェントをどのようにつなぐかを解説します。
- [CRM とケース管理の AI](https://www.objectos.ai/ja/crm-case-management-ai/): CRM とケース管理の AI が既存システム、ビジネスオブジェクト、権限、ワークフロー、AI エージェントをどのようにつなぐかを解説します。
- [レガシーシステム上の製造業 AI](https://www.objectos.ai/ja/manufacturing-ai/): レガシーシステム上の製造業 AI が既存システム、ビジネスオブジェクト、権限、ワークフロー、AI エージェントをどのようにつなぐかを解説します。
- [AI-native App-Plattform](https://www.objectos.ai/de/ai-native-app-platform/): Erfahren Sie, wie AI-native App-Plattform bestehende Systeme, Business Objects, Berechtigungen, Workflows und AI Agents verbindet.
- [Legacy-System-Modernisierung mit AI](https://www.objectos.ai/de/legacy-system-modernization/): Erfahren Sie, wie Legacy-System-Modernisierung mit AI bestehende Systeme, Business Objects, Berechtigungen, Workflows und AI Agents verbindet.
- [Self-Hosted AI für Unternehmensanwendungen](https://www.objectos.ai/de/self-hosted-ai/): Erfahren Sie, wie Self-Hosted AI für Unternehmensanwendungen bestehende Systeme, Business Objects, Berechtigungen, Workflows und AI Agents verbindet.
- [CRM- und Case-Management-AI](https://www.objectos.ai/de/crm-case-management-ai/): Erfahren Sie, wie CRM- und Case-Management-AI bestehende Systeme, Business Objects, Berechtigungen, Workflows und AI Agents verbindet.
- [Manufacturing AI auf Legacy-Systemen](https://www.objectos.ai/de/manufacturing-ai/): Erfahren Sie, wie Manufacturing AI auf Legacy-Systemen bestehende Systeme, Business Objects, Berechtigungen, Workflows und AI Agents verbindet.
- [Plataforma de aplicaciones AI-native](https://www.objectos.ai/es/ai-native-app-platform/): Aprende cómo Plataforma de aplicaciones AI-native conecta sistemas existentes, objetos de negocio, permisos, workflows y agentes AI.
- [Modernización de sistemas heredados con AI](https://www.objectos.ai/es/legacy-system-modernization/): Aprende cómo Modernización de sistemas heredados con AI conecta sistemas existentes, objetos de negocio, permisos, workflows y agentes AI.
- [AI autoalojada para aplicaciones empresariales](https://www.objectos.ai/es/self-hosted-ai/): Aprende cómo AI autoalojada para aplicaciones empresariales conecta sistemas existentes, objetos de negocio, permisos, workflows y agentes AI.
- [AI para CRM y gestión de casos](https://www.objectos.ai/es/crm-case-management-ai/): Aprende cómo AI para CRM y gestión de casos conecta sistemas existentes, objetos de negocio, permisos, workflows y agentes AI.
- [AI industrial sobre sistemas heredados](https://www.objectos.ai/es/manufacturing-ai/): Aprende cómo AI industrial sobre sistemas heredados conecta sistemas existentes, objetos de negocio, permisos, workflows y agentes AI.
- [Plateforme applicative AI-native](https://www.objectos.ai/fr/ai-native-app-platform/): Découvrez comment Plateforme applicative AI-native connecte les systèmes existants, les objets métier, les permissions, les workflows et les agents AI.
- [Modernisation des systèmes hérités avec AI](https://www.objectos.ai/fr/legacy-system-modernization/): Découvrez comment Modernisation des systèmes hérités avec AI connecte les systèmes existants, les objets métier, les permissions, les workflows et les agents AI.
- [AI auto-hébergée pour les applications d’entreprise](https://www.objectos.ai/fr/self-hosted-ai/): Découvrez comment AI auto-hébergée pour les applications d’entreprise connecte les systèmes existants, les objets métier, les permissions, les workflows et les agents AI.
- [AI pour CRM et gestion des dossiers](https://www.objectos.ai/fr/crm-case-management-ai/): Découvrez comment AI pour CRM et gestion des dossiers connecte les systèmes existants, les objets métier, les permissions, les workflows et les agents AI.
- [AI industrielle sur systèmes hérités](https://www.objectos.ai/fr/manufacturing-ai/): Découvrez comment AI industrielle sur systèmes hérités connecte les systèmes existants, les objets métier, les permissions, les workflows et les agents AI.
- [AI-native 앱 플랫폼](https://www.objectos.ai/ko/ai-native-app-platform/): AI-native 앱 플랫폼이 기존 시스템, 비즈니스 객체, 권한, 워크플로, AI 에이전트를 어떻게 연결하는지 설명합니다.
- [AI 기반 레거시 시스템 현대화](https://www.objectos.ai/ko/legacy-system-modernization/): AI 기반 레거시 시스템 현대화이 기존 시스템, 비즈니스 객체, 권한, 워크플로, AI 에이전트를 어떻게 연결하는지 설명합니다.
- [엔터프라이즈 애플리케이션을 위한 셀프 호스팅 AI](https://www.objectos.ai/ko/self-hosted-ai/): 엔터프라이즈 애플리케이션을 위한 셀프 호스팅 AI이 기존 시스템, 비즈니스 객체, 권한, 워크플로, AI 에이전트를 어떻게 연결하는지 설명합니다.
- [CRM 및 케이스 관리 AI](https://www.objectos.ai/ko/crm-case-management-ai/): CRM 및 케이스 관리 AI이 기존 시스템, 비즈니스 객체, 권한, 워크플로, AI 에이전트를 어떻게 연결하는지 설명합니다.
- [레거시 시스템 위의 제조 AI](https://www.objectos.ai/ko/manufacturing-ai/): 레거시 시스템 위의 제조 AI이 기존 시스템, 비즈니스 객체, 권한, 워크플로, AI 에이전트를 어떻게 연결하는지 설명합니다.

## English Articles

- [When an AI Agent Deletes Production Data: Runtime Guardrails Beat Prompts](https://www.objectos.ai/en/blog/when-ai-agent-deletes-production-database/): The Replit database incident shows a structural lesson: an agent's blast radius must be controlled by runtime permissions, approvals, and audit logs, not only by a prompt.
- [Retool vs. Governed AI App Platforms: Can You Review Business Authority?](https://www.objectos.ai/en/blog/retool-vs-ai-native-app-platform/): Retool has strong access governance, including RBAC, audit logs, SSO, and self-hosting. The harder question is whether business authority is declared as a reviewable fact.
- [Power Platform Lock-In: Dataverse, Azure, and the Self-Host Tradeoff](https://www.objectos.ai/en/blog/power-platform-lock-in-dataverse-self-host/): Power Platform is already inside the Microsoft tenant, but self-hosting, Dataverse export, AI usage pricing, and sovereignty requirements matter for long-running systems.
- [Is Lovable Safe for Production? The Access-Control Review Problem](https://www.objectos.ai/en/blog/is-lovable-safe-for-production/): Lovable can turn a sentence into a full-stack app, but production data depends on access control the accountable builder must be able to inspect, understand, and approve.
- [Airtable Omni vs. Governed AI App Platforms: Why Reviewed Diffs Beat Undo](https://www.objectos.ai/en/blog/airtable-omni-vs-governed-ai-app-platform/): Airtable Omni can build a real app from one sentence, but regulated systems of record need reviewed diffs, preventive controls, and infrastructure choices that go beyond undo.
- [AI-Written Apps: Can You Review the Diff and Merge With Confidence?](https://www.objectos.ai/en/blog/ai-wrote-your-app-dare-to-merge/): AI can generate a working app in 30 minutes. The hard part is signing off on an 8,000-line PR you did not write. Reviewability, not speed, is the new moat.
- [How to Write Agent Rules That Generate Governable Apps](https://www.objectos.ai/en/blog/give-your-agent-rules-for-governable-apps/): Most agent rule files police style, not governance. Use AGENTS.md, .cursor/rules, and an open declarative target so AI-generated apps are reviewable from day one.
- [Open vs. Closed Enterprise Ontologies: Who Owns the Business Semantic Layer?](https://www.objectos.ai/en/blog/enterprise-ontology-race-open-vs-closed/): Microsoft, Google, and Palantir are each building enterprise semantic layers. The risk is fragmentation: your customer, order, and device definitions split across platforms.
- [Vibe Coding Technical Debt: Why AI-Built Apps Become Hard to Change](https://www.objectos.ai/en/blog/vibe-coding-technical-debt-2026/): A team's AI-built expense system ran fine for months until tax rules changed and no one dared touch its 12,000 lines of unread code. Why generating definitions beats generating code.
- [EU AI Act Audit Readiness: Can Your AI Runtime Produce Evidence?](https://www.objectos.ai/en/blog/eu-ai-act-runtime-audit/): When an auditor asks for the full record of one AI decision, model quality is not enough. Your runtime must show authorization, evidence, oversight, and audit history.
- [MCP Security for Enterprise Agents: Why Protocols Need Governed Tools](https://www.objectos.ai/en/blog/mcp-governed-tool-layer/): MCP can connect agents to tools quickly, but enterprise systems need identity, permissions, approvals, and audit behind every tool call.
- [Why AI Agent Pilots Fail Before Production: The Four Missing Layers](https://www.objectos.ai/en/blog/why-ai-agent-pilots-fail-four-layers/): A project drew applause on demo day, then was killed four months later by one question from legal. The problem was not the model; it was missing semantics, permissions, approvals, and audit.
- [AI Agent Pricing: Per-Action Billing vs. Self-Hosted Runtime Cost](https://www.objectos.ai/en/blog/enterprise-agent-true-cost/): At $0.10 per Agentforce action, a successful agent can make usage-based pricing rise quickly. Compare per-action billing with a self-hosted runtime before you scale.
- [Agentforce vs. an Open Self-Hosted Runtime: When to Choose Each](https://www.objectos.ai/en/blog/beyond-agentforce-copilot-open-runtime/): A company nearly signed with Agentforce until it found that half its data lived outside the suite. Here is when to choose a closed suite, when to choose open self-hosting, and when to use both.
- [Enterprise AI Ontology: Why the Semantic Layer Should Be an Open Protocol](https://www.objectos.ai/en/blog/ai-ontology-open-protocol/): Palantir proved that AI needs a governed semantic layer to enter the enterprise. As AI writes software and agents choose the stack, it is time to rethink which layer should be open.
- [Metadata, Not Code Generation: What Makes AI-Built Apps Governable](https://www.objectos.ai/en/blog/metadata-not-code-generation/): Code generation can speed up prototypes, but enterprise applications need a metadata runtime where objects, fields, views, permissions, workflows, actions, and agent tools are governed together.
- [From a Sentence to a Governable App: How AI Generates App Metadata](https://www.objectos.ai/en/blog/natural-language-to-app-metadata/): The important part of AI Builder is not turning one sentence into pages, but decomposing a business request into objects, fields, views, workflows, permissions, automation, and agent tools.
- [Airtable-Style AI App Builder: Build by Table, Change by Chat](https://www.objectos.ai/en/blog/airtable-style-ai-builder/): A strong AI app builder combines table-based app building with natural-language iteration, while keeping objects, fields, views, permissions, and automation visible.
- [Edit Business Systems by Conversation: Add Fields and Change Flows](https://www.objectos.ai/en/blog/conversational-app-iteration/): The real value of an AI builder is continuous conversational iteration: fields, workflows, views, permissions, and automation evolve through reviewable metadata changes.
- [AI Ticket Hub: Build a Support System That Actually Reads the Customer's Problem](https://www.objectos.ai/en/blog/ai-ticket-hub/): A support system should do more than queue issues. With metadata for cases, messages, SLA, knowledge, permissions, and agent tools, AI can understand customer problems and move work forward safely.
- [AI Sales Assistant: How to Update CRM Records and Suggest Next Steps](https://www.objectos.ai/en/blog/ai-sales-assistant/): An AI sales assistant is not just auto-fill for CRM. Natural language can generate accounts, contacts, opportunities, activities, tasks, and agent tools so sellers work through conversation.
- [AI Project Management Assistant: Surfacing the Risk Hidden in Status Updates](https://www.objectos.ai/en/blog/ai-project-risk-assistant/): An AI project assistant is not another board. It models projects, tasks, meetings, risks, changes, and action plans so AI can detect delays and blockers from everyday updates.
- [AI Procurement Risk: How to Spot Supplier Risk Before Approval](https://www.objectos.ai/en/blog/ai-procurement-risk/): An AI procurement decision app should not hide behind one supplier score. It should connect qualifications, quotes, contracts, orders, delivery, quality, and risk evidence into a conversational decision layer.
- [AI Expense Audit: Build a Finance App That Understands Policy, Not Just OCR](https://www.objectos.ai/en/blog/ai-expense-audit/): AI expense review is not only invoice recognition. It should model policies, budgets, projects, approvals, anomaly patterns, and audit records so finance can explain every recommendation.
- [AI Employee Service Center: How to Move Beyond HR, IT, and Admin Tickets](https://www.objectos.ai/en/blog/ai-employee-service-center/): An AI employee service center is not a chat wrapper over HR, IT, and admin tickets. It models service catalogs, knowledge, requests, approvals, and governed agent actions.
- [AI Contract Review: Build an App That Flags Clause and Obligation Risk First](https://www.objectos.ai/en/blog/ai-contract-risk/): The value of an AI contract app is not summarization. It is turning contract types, clauses, obligations, risk rules, approvals, and audit into metadata that legal and business teams can use together.
- [AI Content Workbench: From Ideas to Publishing and Retrospectives](https://www.objectos.ai/en/blog/ai-content-workbench/): Content teams need more than a writing box. Natural language can build topics, sources, briefs, drafts, reviews, publishing, and metrics so AI participates in the full content workflow.
- [AI Compliance and Internal Controls: Stop Checking Policies by Hand](https://www.objectos.ai/en/blog/ai-compliance-control/): An AI internal control app is not only policy Q&A. It turns policy clauses, controls, evidence, gaps, remediation, and audit records into a closed-loop compliance workflow.
- [AI Agent Workbench: How Agents Execute Tasks Inside Business Systems](https://www.objectos.ai/en/blog/ai-agent-workbench/): Enterprise agents must do more than chat. They need business objects, tools, permissions, approvals, and audit boundaries so natural-language intent can become controlled execution.
- [Self-Hosted AI Application Platforms: Why the Runtime Belongs to You](https://www.objectos.ai/en/blog/self-hosted-ai-app-platform/): Once AI reads business data, triggers workflows, generates applications, and calls tools, enterprises need control over the runtime that governs objects, permissions, tools, approvals, and audit evidence.
- [From Requirement to Running App: How AI Generates Reviewable Metadata](https://www.objectos.ai/en/blog/from-requirement-to-app/): A concrete equipment repair scenario shows how AI Builder turns one request into objects, fields, relationships, views, permissions, actions, workflows, APIs, and agent tools.
- [How AI Agents Stay Inside Enterprise Permission Boundaries](https://www.objectos.ai/en/blog/ai-agent-business-data-security-boundaries/): Enterprise teams do not need AI agents to become unrestricted administrators. They need agents that act as controlled users, inherit permissions, route risky actions for approval, and leave an audit trail.
- [AI for Legacy Manufacturing Systems: Start With Reports and Work Orders](https://www.objectos.ai/en/blog/manufacturing-legacy-systems-ai/): Manufacturing systems are hard to replace. A practical AI path connects existing systems and starts with reports, work orders, and exception analysis.
- [Low-Code vs. AI-Native App Platforms: Where Complex Business Breaks](https://www.objectos.ai/en/blog/low-code-vs-ai-native-app-platform/): Low-code helps teams build pages and workflows faster, but complex business systems depend on objects, permissions, integrations, change control, and maintainability.
- [AI for CRM: How Agents Read Customer Data Without Bypassing Permissions](https://www.objectos.ai/en/blog/crm-ai-understands-customers/): Most CRMs already hold customer, opportunity, contact, and activity history. The useful path is to let AI understand those business objects under existing permissions.
- [Add AI to Existing Systems Without Migration: Connect Your Database](https://www.objectos.ai/en/blog/extend-existing-systems-with-ai/): Connect ObjectOS to the database you already run, let a coding agent model the tables as objects, and put AI on real data under your permissions, on your servers, with the original system untouched.

## Simplified Chinese Articles

- [AI 智能体删除生产数据：为什么运行时护栏比提示词可靠](https://www.objectos.ai/zh-Hans/blog/when-ai-agent-deletes-production-database/): 公开记录中的 Replit 事故提醒我们：智能体的影响半径不能只靠提示词收窄。生产数据、破坏性操作和恢复证据，都需要由运行时权限、审批和审计来约束。
- [Retool 与受治理 AI 应用平台：能否审查业务权限](https://www.objectos.ai/zh-Hans/blog/retool-vs-ai-native-app-platform/): Retool 的 RBAC、审计日志、SSO 和自托管能力很强。真正要比较的是业务权限层：退款、审批、写入动作如果散落在 JavaScript 绑定里，AI 改动就很难被业务负责人用 diff 审查。
- [Power Platform 锁定：Dataverse、Azure 与自托管取舍](https://www.objectos.ai/zh-Hans/blog/power-platform-lock-in-dataverse-self-host/): Power Platform 的优势是真实的：身份、Teams、Dynamics 和账单都在同一个租户里。但若你关心主权、规模化成本或 AI 改动审查，Dataverse 和 Azure 运行时就是必须提前算清的边界。
- [Lovable 上生产安全吗：访问控制审查问题](https://www.objectos.ai/zh-Hans/blog/is-lovable-safe-for-production/): Lovable 很适合快速原型，但生产系统的问题不是能不能跑，而是谁能审查访问控制。RLS、前端过滤和安全扫描都重要；真正的边界必须在服务端可见、可强制、可签字。
- [Airtable Omni 与受治理 AI 应用平台：为什么审阅 diff 比撤销更重要](https://www.objectos.ai/zh-Hans/blog/airtable-omni-vs-governed-ai-app-platform/): Airtable Omni 把自然语言和表格式应用结合得很强。记录系统真正要比较的，不是能不能生成应用，而是 AI 改动权限、字段和流程时，是否能在上线前形成可审阅的 diff。
- [AI 写完应用之后：你敢审查 diff 并点 Merge 吗？](https://www.objectos.ai/zh-Hans/blog/ai-wrote-your-app-dare-to-merge/): AI 可以很快生成能跑的应用，CI 也可能全绿。真正的问题是：那份几千行、没人完整理解的 PR，谁敢负责合并？当写代码被自动化，瓶颈就从“写”转向“审查与签字”。
- [Agent 规则文件怎么写：让 AI 生成可治理应用](https://www.objectos.ai/zh-Hans/blog/give-your-agent-rules-for-governable-apps/): 编码 agent 的 AGENTS.md、.cursor/rules 或 CLAUDE.md 不该只管代码风格。把权限、审批、审计和目标元数据格式写进去，AI 生成的应用才更容易被审查和签字。
- [开放与封闭企业本体：谁拥有业务语义层](https://www.objectos.ai/zh-Hans/blog/enterprise-ontology-race-open-vs-closed/): 企业 AI 需要机器可读的业务定义层。但如果“客户、订单、设备”的定义分别锁在不同平台里，agent 看到的就不是同一家公司。语义层应当归企业自己，而不是归某个套件。
- [Vibe Coding 技术债：为什么 AI 生成的应用后来难改](https://www.objectos.ai/zh-Hans/blog/vibe-coding-technical-debt-2026/): AI 生成代码能让原型很快上线，但长期系统的问题在半年后出现：没人完整读过那一万多行实现，也没人能解释当初的业务取舍。企业应用需要生成可审查的定义，而不是难维护的黑箱代码。
- [EU AI Act 审计准备：你的 AI 运行时能交出证据吗](https://www.objectos.ai/zh-Hans/blog/eu-ai-act-runtime-audit/): AI Act 的多数规则按官方时间线将在 2026 年 8 月 2 日适用。审计真正要看的不是模型多强，而是运行时能否交出谁授权、动了什么、证据在哪。
- [MCP 安全：为什么协议还需要受治理的工具层](https://www.objectos.ai/zh-Hans/blog/mcp-governed-tool-layer/): MCP 和 A2A 让 agent 连接工具与其他 agent 变得更容易，但连接不等于授权。企业缺的不是再包一层接口，而是每次调用都带身份、强制权限、留下审计的工具层。
- [为什么 AI Agent 试点进不了生产：缺的是四层运行基础](https://www.objectos.ai/zh-Hans/blog/why-ai-agent-pilots-fail-four-layers/): 一个 agent 演示可以很精彩，生产评审却只问一件事：你怎么证明它不会越权、会等审批、能交出审计证据？试点失败通常不是模型不够强，而是缺语义、权限、审批和审计四层。
- [AI Agent 定价：按动作计费与自托管运行时成本](https://www.objectos.ai/zh-Hans/blog/enterprise-agent-true-cost/): 按动作或按 token 计费看起来灵活，但 agent 越自主，中间工具调用越多。真正的成本账要同时看用量曲线、数据出域、平台锁定，以及什么时候自托管才划算。
- [Agentforce、Copilot Studio 之外：何时选择开放自托管运行时](https://www.objectos.ai/zh-Hans/blog/beyond-agentforce-copilot-open-runtime/): Agentforce、Copilot Studio、ServiceNow AI Agents 在各自生态内都很强。问题是你的数据、流程和权限是否也在同一个生态内；若不是，开放自托管运行时或混合架构可能更稳。
- [企业 AI Ontology：为什么业务语义层应该是开放协议](https://www.objectos.ai/zh-Hans/blog/ai-ontology-open-protocol/): AI 进入企业需要受治理的业务语义层，这个判断已经越来越清楚。真正要重新思考的是形态：业务定义应当开放、可审查、可迁移；运行时可以收费并承担执行责任。
- [跨系统自动化：连接器和 Webhook 如何进入受治理流程](https://www.objectos.ai/zh-Hans/blog/automation-cross-system-flows/): CRM、ERP、合同、财务和外部服务都在流程里。可靠的自动化引擎不是多接几个 API，而是把外部调用、失败补救和审计放进同一条业务流程。
- [自然语言改流程：自动化引擎如何治理变更](https://www.objectos.ai/zh-Hans/blog/automation-governed-flow-changes/): 自然语言可以降低流程修改门槛，但不能让流程直接上线。可靠的自动化引擎要把每次变更变成可审查、可校验、可发布、可回滚的流程元数据。
- [自动化触发模型：数据变化、定时、按钮和 API 如何进入同一流程](https://www.objectos.ai/zh-Hans/blog/automation-trigger-model/): 流程可以由记录变化、定时计划、人工按钮、Webhook 或 API 调用触发。成熟的自动化引擎要统一入口后的业务规则，避免同一流程在多个地方重复实现。
- [审批与暂停恢复：自动化引擎为什么必须会等待](https://www.objectos.ai/zh-Hans/blog/automation-pause-resume-approvals/): 企业流程经常要等人审批、等用户补材料、等时间到达或等外部结果。自动化引擎只有支持暂停和恢复，才能把这些等待放进同一条完整流程。
- [AI 自动化流程：如何判断、等待并留下证据](https://www.objectos.ai/zh-Hans/blog/objectos-automation-engine/): 企业需要的自动化不是简单触发器，而是能把业务规则变成可审批、可等待、可恢复、可审计的流程元数据。ObjectOS 让 AI 生成的流程进入业务运行时。
- [AI 如何触发业务动作：Action 元数据如何保证受控执行](https://www.objectos.ai/zh-Hans/blog/objectos-action-tools/): AI agent 的价值不只是回答问题，而是帮助用户更新记录、创建任务、发起审批和推动流程。ObjectOS 用 Action 元数据把按钮、流程和审批开放给 AI，同时保留权限、确认和审计。
- [AI Agent 权限边界：数据和动作如何受运行时约束](https://www.objectos.ai/zh-Hans/blog/objectos-agent-permission-boundaries/): 企业 AI agent 可以查数据、发起动作，但必须继承用户权限，遵守记录范围、字段级安全、动作确认和审计要求，不能成为系统后门。
- [元数据，不是代码生成：AI 应用为什么可治理](https://www.objectos.ai/zh-Hans/blog/metadata-not-code-generation/): 代码生成能让原型变快，但企业应用真正需要的是对象、字段、关系、视图、权限、流程、动作和 agent 工具共同受控的元数据运行时。
- [从自然语言到应用元数据：AI Builder 如何生成对象和权限](https://www.objectos.ai/zh-Hans/blog/natural-language-to-app-metadata/): AI Builder 真正重要的不是把一句话变成页面，而是把业务需求拆成对象、字段、视图、流程、权限、自动化和 agent 工具。
- [Airtable 式 AI Builder：用表格理解应用，用对话修改应用](https://www.objectos.ai/zh-Hans/blog/airtable-style-ai-builder/): 最好的 AI Builder 把表格式搭建、对话式修改和受治理的元数据结合起来：对象、字段、视图、权限和自动化都可见，也都能被审查。
- [对话式应用迭代：加字段、改流程、生成视图和自动化](https://www.objectos.ai/zh-Hans/blog/conversational-app-iteration/): AI Builder 的真正价值不是“聊一句就改”，而是把字段、流程、视图、权限和自动化都落到可审查、可回滚的元数据层。
- [AI 工单中枢：让客服系统读懂客户问题](https://www.objectos.ai/zh-Hans/blog/ai-ticket-hub/): 客服工单不应该只负责排队。把对象、队列、SLA、知识库和受控工具做成元数据后，AI 才能在权限边界内理解问题、推荐回复并推动流转。
- [AI 销售助理：如何更新 CRM 并建议下一步](https://www.objectos.ai/zh-Hans/blog/ai-sales-assistant/): AI 销售助理不只是自动填表，而是把客户、联系人、商机、跟进和任务做成可治理的元数据，让销售用对话推进商机，同时保留权限和审计。
- [AI 项目管理助手：从进度更新里发现风险](https://www.objectos.ai/zh-Hans/blog/ai-project-risk-assistant/): AI 项目助手的价值不是再做一个看板，而是把项目、任务、会议、风险、变更和行动计划做成对象，从日常更新中识别延期和阻塞。
- [AI 采购风险：下单前看见供应商风险](https://www.objectos.ai/zh-Hans/blog/ai-procurement-risk/): AI 采购应用不只是给供应商打分，而是把供应商、资质、报价、合同、履约和风险做成元数据，让采购在下单前看见依据。
- [AI 报销审核：理解政策，而不只是识别发票](https://www.objectos.ai/zh-Hans/blog/ai-expense-audit/): AI 报销审核不止识别发票，而是把费用政策、预算、项目、审批、异常模式和审计记录做成元数据，让财务能解释和处理风险。
- [AI 员工服务中心：从 HR/IT 工单到可执行服务](https://www.objectos.ai/zh-Hans/blog/ai-employee-service-center/): AI 企业服务中心不是把 HR、IT、行政工单换成聊天框，而是把服务目录、知识库、申请对象、审批流和受控动作做成可执行服务。
- [AI 合同审查：先标风险，再让法务签字](https://www.objectos.ai/zh-Hans/blog/ai-contract-risk/): AI 合同应用不只是总结合同，而是把合同类型、条款、义务、风险规则、审批和审计做成元数据，让 AI 标风险、法务确认责任。
- [AI 内容工作台：从选题到发布与复盘](https://www.objectos.ai/zh-Hans/blog/ai-content-workbench/): 内容团队需要的不是孤立写作框，而是把选题、素材、草稿、审核、发布和复盘做成对象，让 AI 参与完整内容运营流程。
- [AI 内控检查：把制度变成可追溯控制](https://www.objectos.ai/zh-Hans/blog/ai-compliance-control/): AI 内控应用不是制度问答，而是把制度条款、控制点、证据、缺口、整改和审计做成对象；AI 发现缺口，人确认责任，运行时保留证据链。
- [AI Agent 工作台：让 agent 在业务系统内受控执行](https://www.objectos.ai/zh-Hans/blog/ai-agent-workbench/): 企业 agent 不能只是会聊天，而要能在业务对象、工具、权限、审批和审计边界内执行任务。工作台的关键是受控执行，而不是万能权限。
- [自托管 AI 应用平台：为什么运行时属于你](https://www.objectos.ai/zh-Hans/blog/self-hosted-ai-app-platform/): 当 AI 开始读取业务数据、触发流程、生成应用和调用工具，企业真正要控制的不只是模型，而是承载对象、权限、工具、审批和审计的运行时。
- [从需求到可审查应用：AI 如何生成 ObjectStack 元数据](https://www.objectos.ai/zh-Hans/blog/from-requirement-to-app/): 用设备报修场景拆开 AI Builder 的生成过程：对象、字段、关系、视图、权限、动作、流程、API 和 agent 工具如何由同一份元数据驱动。
- [AI Agent 数据安全边界：如何在企业权限内工作](https://www.objectos.ai/zh-Hans/blog/ai-agent-business-data-security-boundaries/): 企业不是不想让 AI agent 使用业务数据，而是不允许它绕过身份、权限、审批和审计。真正可上线的 agent，必须像一个受控用户，而不是影子管理员。
- [制造业既有系统怎么接 AI：先从报表和工单开始](https://www.objectos.ai/zh-Hans/blog/manufacturing-legacy-systems-ai/): 制造业系统链路复杂，ERP、MES、WMS、设备台账和工单系统都不能轻易替换。更务实的 AI 路线，是先连接现有系统，从报表、工单和异常分析切入。
- [低代码 vs AI 原生应用平台：复杂业务卡在哪里](https://www.objectos.ai/zh-Hans/blog/low-code-vs-ai-native-app-platform/): 低代码解决的是更快搭页面和流程；复杂业务真正卡住的是对象、权限、集成、变更和可维护性。AI 原生平台要把这些变成可审查的运行时元数据。
- [CRM AI：让 agent 在权限内读取客户和商机](https://www.objectos.ai/zh-Hans/blog/crm-ai-understands-customers/): 很多公司的 CRM 里已有客户、商机、联系人和跟进记录。真正有价值的做法不是导出数据问一次，而是让 agent 在权限之下读懂这些业务对象。
- [定制系统技术债：为什么半年后没人敢改](https://www.objectos.ai/zh-Hans/blog/why-custom-systems-die/): 很多内部系统不是越用越顺，而是越用越僵。根因往往不在程序员，而在业务规则被埋进代码里，后续既难审查，也难让 AI 安全修改。
- [给现有系统加 AI：连接数据库，而不是先迁移](https://www.objectos.ai/zh-Hans/blog/extend-existing-systems-with-ai/): 把 ObjectOS 连到已经运行的数据库，让 agent 把关键数据表建模为对象，再在你的权限和服务器边界内叠加 AI 能力；原系统继续运行，AI 走受控对象层。

## Policies

- [Terms](https://www.objectos.ai/en/terms/)
- [Privacy](https://www.objectos.ai/en/privacy/)