- 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
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Customer Success
- FlowFuse for Education
- Hubspot
- Marketing
- How we work
- Video
- Customer Stories
- Community
- blog
- Lead Generation
- Social Media
- Marketing - Website
- Webinars
- Trade Shows
- FlowFuse Messaging
- Brand Voice
- Sales
- 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
# Tools
# GitHub
This is at the heart of how we work. Everyone in the company will be made part of the FlowFuse organization as part of their on-boarding activities.
# LLM Programming assists
FlowFuse recognizes the potential of LLM (AI) tools to increase productivity and innovation. When using these tools, understand that the author and committer of any work remains fully responsible for its quality, functionality, and security. AI-assisted work must meet the same high standards as work written entirely by a human. Review each line of code before committing.
When using AI tools for development, never share:
- Personal Identifiable Information (PII)
- Company secrets like API keys, private credentials, etc, etc.
- Customer code or other assets under NDA
# GitHub Copilot
We do not currently provide organization-wide licenses for GitHub Copilot, but if team members wish to purchase an individual license they can do so and expense the cost.
As it stands, some of the team already have Copilot access via their Open Source work at no cost. To enable it at the organization level will cost almost twice that of individual access; and currently the benefits do not justify that increased cost.
We will keep this under review - if you feel we are missing out by not having the organization level access, please speak to the CTO.