# Your data platform, running itself.

Amfelt discovers sources and creates contracts in an open standard, then generates layers, history, and load logic on your infrastructure.

## Coming soon — Your data platform, running itself.

Amfelt discovers your sources and creates the data contracts that drive generated layers and load logic. Your team chooses how each dataset keeps its history, while an agent runs the data work on your infrastructure.

Links: [Join the waitlist](/waitlist/) [Try the live demo](https://demo.amfelt.com/)

## See changes clearly

Review open-standard contracts in Git. Rerun discovery to see how sources changed and assess their impact.

## Build on generated foundations

Amfelt generates data layers and history logic from your contracts, with documentation you can enable.

## Run where your data lives

Your agent moves and structures data on your infrastructure. Configure and monitor jobs from Amfelt’s cloud control plane.

## Platform — More time to build your data products.

Amfelt connects discovery, data movement, and generated layers through your source contracts. With configurable history and generated documentation you can enable, your team gets a consistent foundation for analytics and business models.

## Live demo

[Open preview](https://demo.amfelt.com/)

## AI-ready by design — Give your AI tools context from the source.

Amfelt creates open-standard contracts from your sources. Enable generated documentation and diagrams to give your team and AI tools a shared reference for the data your pipelines handle.

### Open-standard contracts

Dataset structures and relationships described in the Open Data Contract Standard, ready to review and version in Git.

### Context your tools can read

Enable generated Markdown documentation and relationship diagrams, readable by your team and usable by AI tools.

### Checks with every sync

Each sync compares the extracted schema with its contract and reconciles loaded record counts. Differences are reported for review.

### Semantics and governed access

On the roadmap: semantic definitions through Apache Ossie and governed agent access over MCP (Model Context Protocol).

Links: [AI-ready data](/solutions/ai-ready-data/)

## Integrations — Connect your sources and destinations.

Amfelt builds and maintains its connectors in-house. Explore the source and destination support available for your platform. Your feedback helps guide which integrations we build next. [Usage-based plans](/pricing/) include all supported connectors.

Links: [All integrations](/integrations/)

## From the team — We build data tools. We also have opinions about them.

- [Amfelt's first version is ready for closed testing](/blog/first-version-closed-testing/)
- [The board wants AI. The data is still on the ship.](/blog/why-we-are-building-amfelt/)
- [How we keep parallel agents working toward the same plan](/blog/coordinating-parallel-agents/)
- [Type casting belongs between the L and the T](/blog/type-casting-is-a-pipeline-step/)

[More articles](/blog/)

## Join the Amfelt waitlist.

We’re preparing Amfelt for its first teams. Join the waitlist to hear when access becomes available.

Links: [Join the waitlist](/waitlist/)