How we work

Build with Fabric.
Help when you need it.

Build your own workflows with Fabric and Fabric Agent. Get hands-on engineering support when you need it, while Paneo runs the infrastructure.

Discuss your project

Timing & cost

Your estimate separates the managed platform from any assessment or engineering support you choose. Data volume, processing, storage, and support needs shape the monthly cost.

Discuss your project

Before we start

A few practical
questions.

Which inputs can Fabric work with?

Fabric connects to gateways, APIs, files, and streams. A representative sample lets us check the connector, format, volume, and processing your project needs. Device communications and specialized scientific processing can stay in your existing systems.

Can we keep our existing tools?

Yes. Fabric can take inputs from your existing systems and deliver outputs back to them. We identify where it fits around the tools your team already uses.

Can we build and change workflows ourselves?

Yes. Fabric is designed for your team to connect data, configure processing, and publish outputs directly. Fabric Agent helps draft and adapt workflows; the nodes and connections remain visible and editable. If you want hands-on help, a Paneo engineer can pair with your team on integration, workflow design, or troubleshooting. That support is optional.

Who runs and supports the infrastructure?

Paneo runs the Fabric deployment. Before launch, we define deployment location, monitoring, maintenance, incident handling, support contacts, and escalation. Your team builds and controls its workflows and operates its devices and upstream systems.

What can we inspect, and what history is retained?

Sources, node settings, joins, and output configuration are visible in the workflow. Historical evidence is a separate requirement: permissions, change history, execution provenance, and retention need to be confirmed for your deployment. A visible configuration alone does not establish which version produced a past result. We review the coverage your deployment needs with you.

How are access and data ownership handled?

You retain your data rights and customer relationships. Together we establish who may use each source, who needs access, and what each customer receives. Bring any residency, retention, or exit requirements into deployment planning.

What determines the cost?

Data volume, processing, storage, delivery interfaces, and support requirements affect the cost. Your estimate separates the managed platform from any paid assessment, guided sessions, or integration support you choose.

What do we need for a first conversation?

A few lines about your project, the data you have, and what you want to make possible. A deadline is useful if you have one. We can discuss getting started in Fabric and whether guided sessions or a paid integration assessment would be useful.