FlowFuse / FlowFuse/flowfuse

Database Offerings

Open
#4,911 9 comments 0 reactions 2 assignees Assigned to @knolleary View on GitHub
12-month-plan epic headline scope:enterprise
Dominant language
JavaScript
Stars
400
Forks
89
Avg merge
1d 20h
Merged PRs (30d)
149

Description

Alongside our Broker offering, we'd be looking to offer a database too, or at least integrate and provide enhanced UX around existing DBs.

Where possible, especially as a first iteration, we'll be looking at partner technologies/offerings here.

```[tasklist]
### Tasks
- [ ] Historian/Timeseries Database Offering
- [ ] Structure/SQL Database Offering
```

Requested by:

-https://app-eu1.hubspot.com/contacts/26586079/record/0-1/209119058119

Greg edit June 5 2025:

A database offering within FlowFuse serves two distinct needs:
- Storage is an important component of many applications
- Storage is a critical part of industrial applications that serve our ICP. UNS, MES, SCADA, and ERP systems all have a database component.

For these reasons, a database offering of some kind is a needed part of our overall feature set.

In keeping with our overall product strategy, a FlowFuse database offering should be general enough that it is not limited to the specific purposes of any particular industrial application, but is compatible with all of them.

As we are moving this work forward quickly, there are important questions that are unanswered for now, but will be filled in as we move forward. They include:

- To what extent are we offering a database?
- Pricing?
- Technology selection?
- MVP offering

**Notes**
FFC Pro customer on value of database offering: https://fathom.video/calls/322651422

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.