Application data foundation
MetaFabric can be the data foundation for your applications. One place holds both the app's own records and data from your connected systems, behind one set of APIs and access rules.
How apps use it#
- 1
Model#
Choose or add the business classes the app uses.
- 2
Connect#
Issue an API key or OAuth client with the right role and scopes.
- 3
Read and write#
Work with records through the Data API.
- 4
React#
Subscribe to changes, or run a function when a record changes.
Applications and services use the Data API with an API key or OAuth client. AI assistants such as Claude and ChatGPT use MCP instead, signed in as a person.
What apps can do#
Create and manage records that exist only in MetaFabric.
Useful when: an app needs its own data, such as orders or requests, without a separate database.
Update records copied in from a source. The change is made in MetaFabric only.
Useful when: MetaFabric is now the main system for that data.
For connectors that support it, an edit is sent to the original system first and saved only if that system accepts it.
Useful when: the source stays the main system and must hold the change.
Live change events keep screens and services current. Admins can attach a function that runs when a record is created, changed or deleted: sandboxed, with no network or file access, 10 seconds per run, and a dry-run mode for testing.
Useful when: a change should notify, recalculate or update another system.
For availability and limits, see Capabilities at a glance.
Access and history#
- API keys and OAuth clients belong to one workspace. They can only do what their role, object permissions and scopes allow.
- They cannot read classes protected by record owner rules, because those rules are tied to a person. See Security, access and tenancy.
- Changes to a record are stored field by field, with the person, key or client that made them.