- handbook
- Company
- Company
- Board & Investors
- Communications
- Decision making and project management
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Incident Response Plan
- Cryptography Policy
- Secure Development Policy
- Access Control Policy
- Information Security Policy and Acceptable Use Policy
- Data Management Policy
- strategy
- values
- Operations
- Product
- Blueprints
- Feedback
- Market Segments
- Metrics
- Node-RED Dashboard
- Personas
- Pricing Principles
- Principles
- Strategy
- Versioning
- Engineering & Design Practices
- Design
- Engineering
- Certified Nodes
- Contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Deployment
- Incident Response
- Observability
- FlowFuse Dedicated
- Staging Environment
- Production Environment
- Project Management
- Releases
- Security Policy
- Team NPM Registry
- tools
- Website A/B Testing
- Internal Operations
- People Ops
- Coaching Plans
- Code of Conduct
- Compensation
- Expenses
- Hiring
- Holiday & Leave
- Job Descriptions
- CEO
- Solutions Engineer
- CTO
- Account Executive
- Product Marketer
- Product Manager
- Engineering Manager
- Developer Relations Advocate
- PeopleOps Policies
- Performance review
- Summit
- Marketing department
- Marketing
- blog
- Brand Voice
- Community
- Company Messaging
- Customer Stories
- FlowFuse for Education
- How we work
- Lead Generation
- Marketing - Website
- Marketing Programs
- Social Media
- Trade Shows
- Video
- Webinars
- Sales department
- Sales
# Releases
- Release Process - Instructions for creating a release are found in the Release Process
- Digital Ocean - How to deploy to Digital Ocean
# Node-RED Dashboard 2.0
- Dashboard Release Process - Release instructions for the Dashboard 2.0
# Beta Release
FlowFuse will release features in beta when it is known to be an early version that may lack features or functions that are intended to be made available at a later date. Pricing is generally a follow up function, and thus things might be released as Beta without pricing, where later the company might charge for the feature. The goal of releasing a feature in beta is that it provides for rapid learning of how users engage with the feature, as this informs later product development.
Beta features can only be introduced in tiers where we expect them to remain once they are successful. If no clear tier can be established for a beta feature, it must be introduced in the Enterprise tier, as moving features down to lower tiers is easier than moving them up. All beta features will be introduced in the licensed, non-open source version to allow the company the freedom to change things as needed.
Features initially released as beta versions may later be deprecated entirely, drastically reconfigured, priced differently, or in other ways very significantly revised compared to their initial beta version.