Any Data Source, One Interface

Business data is scattered. Internal records live in your application database. Operational metrics live in a monitoring service. Traffic data lives in an analytics platform. Infrastructure status lives in a cloud provider. Combining this data into a useful view has traditionally required custom integration work for every combination.

Swifty's unified data source interface eliminates that work.

One Interface, Any Origin

Every data source in Swifty — regardless of where the underlying data lives — presents the same interface to components:

• Provide a list of items with consistent structure
• Support filtering by field value
• Support sorting by field
• Support pagination

That's the contract. Whether the implementation queries a database, calls an API, fetches from a monitoring endpoint, or reads from a static configuration — the component consuming the data doesn't know or care. It requests data through the unified interface and receives items in a consistent shape.

What "Same Components" Means

A table component works with any data source. Connect it to your order database and it shows orders. Connect it to a monitoring API and it shows infrastructure metrics. Connect it to an analytics data source and it shows traffic by page.

A metrics card works with any data source. An aggregation query on your own records, or an aggregation call to an external service — same component, different source.

A chart works with any data source. Time-series data from a monitoring endpoint renders in the same chart component as time-series data from your own records.

Configuration, Not Integration Code

Connecting a new data source to a component is configuration in the builder. Select the source type, enter the connection parameters, configure filters and sorting. The connection is live immediately.

There's no integration code to write, no adapter to build, no deployment to schedule. The source type registers its implementation against the unified interface; configuration connects it to the component.

Growing Source Library

The available data source types expand with each platform update and through the extension system. New source types — when added — immediately work with every existing component. The value of each addition is multiplied by everything that already consumes the unified interface.

The goal is a platform where any useful business data is a configuration step away from appearing in a view alongside your own records.