Tenant isolation
Helps operators prove which customer workspace owned the data and action.
Schema-per-tenant business data with explicit tenant context at runtime
联系销售
请求 ERPStack 商业评审。
使用此路径根据您的买家优先事项评估 ERPStack：模块安装、自托管控制、安全证据、服务操作以及生产部署决策之前所需的剩余暂存或提供商签核。
商业准备边界
本次评审范围
1
Share buyer context
Identify tenant count, target modules, data residency needs, operator roles, and rollout constraints.
2
Review product proof
Walk through finance, operations, workforce, BI, security, and module pages against app routes.
3
Confirm readiness boundary
Separate implemented and locally verified capabilities from staging, provider, and release signoff.
4
Plan next evidence
Define staging target, SIEM endpoint, provider credentials, owner approval, and acceptance checks.
商业评审请求
提交买家背景信息以进行本地审核交接。此页面验证请求，但生产 CRM 或电子邮件传送仍然需要在实时接收之前进行提供商配置。
Module fit review
Validate which ERPStack modules match the buyer's operating model.
Security and trust evidence
Review tenant isolation, RBAC, audit, SIEM, and observability evidence.
Self-hosted readiness
Review infrastructure, backup/restore, rollback, and owner signoff needs.
Migration planning
Compare current systems, integrations, data migration, and rollout phases.
信任证据
审查应基于具体的控制措施，而不是模糊的主张。
ERPStack 将实施的产品证据、本地验证、集成准备和分阶段签核分开，以便商业审查保持可信。
RBAC and workflow control
Keeps privileged work explainable before finance, HR, inventory, or platform actions land.
Role checks, approval paths, read-only gating, and destructive-action contracts
Audit and replay protection
Reduces duplicate external callbacks and preserves reviewable records for sensitive work.
Audit trails, idempotency, provider reference uniqueness, and export evidence
SIEM and incident evidence
Lets service operators see who did what, in which tenant, whether it was blocked, and why.
ERPStack security events, Wazuh proof references, incident triage, notes, and SLA lanes
Observability and traceability
Connects failed jobs, provider issues, security incidents, and release evidence to operations review.
Grafana dashboards, Loki log references, Tempo trace IDs, source-health and backlog signals
Self-hosted operations posture
Supports organizations that need infrastructure ownership instead of cloud-only ERP dependency.
PostgreSQL-centered deployment design, health checks, backup/restore and rollback evidence
Before production signoff
A commercial review is not the same thing as deployment approval.
Final release approval still needs the real staging URL, staging database, external SIEM endpoint credentials when applicable, provider credentials, backup/restore evidence, rollback/reapply proof, performance smoke, and release-owner approval.
| 就绪状态标签 | 商业含义 |
|---|---|
| Implemented | Feature exists in the current app and has local verification evidence |
| Locally verified | Verified with focused tests and/or browser smoke in local environment |
| Integration ready | Code path exists, external provider or production endpoint signoff may be pending |
| Staging signoff pending | Requires real staging target, database, owner approval, or external credentials |