- handbook
- Company
- Company
- Board
- Communications
- Decision making
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Cryptography Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Secure Development Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Information Security Policy and Acceptable Use Policy
- strategy
- values
- Operations
- Product
- Feedback
- Metrics
- Node-RED Dashboard
- personas
- Plan
- Pricing Principles
- Product Categories
- Strategy
- Versioning
- Development & Design Practices
- Design
- Development
- contributing
- Front End
- How We Work
- Markdown How-To
- packaging
- Releases
- security
- staging
- Using Git
- Website A/B Testing
- Internal Operations
- Legal
- People Ops
- Sales & Marketing
- Marketing
- blog
- Boiler Plate Descriptions
- Content Channels
- Content Types
- HubSpot
- Marketing
- Marketing - Website
- Video
- Webinars
- sales
# Data at FlowFuse
At FlowFuse we're trying to leverage data obtained to make better decisions.
# Data sources
Right now we're mostly using the Telemetry data from self-managed installs of FlowFuse. Later we'll likely add data from Stripe and Hubspot.
# Data warehouse
For now the data is imported manually into Big Query. In big query materialized views are created - read; we're processing the data for more, derived, data. As the data is then in the Google realm, it is available as a data source in Google Sheets and Data Studio.
# Source to sink
We've adopted Meltano to obtain and transfer the data. See also the FlowFuse-Data (Internal project) on how we transfer the data. It's manually triggered for now.