- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- strategy
- values
- Operations
- Product
- Feedback
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Product Categories
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Boiler Plate Descriptions
- Marketing - Website
- Customer Stories
- Webinars
- Social Media
- blog
- Sales
- Engineering & Design Practices
- Design
- Engineering
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Project Management
- Releases
- Security Policy
- tools
- Internal Operations
- People Ops
# Production Environment
Our production environment runs in EU-West-1 in a dedicated AWS account.
Access to the AWS account is restricted and not generally available. If you believe you have a need to access the AWS account, raise an Access/Permission Request issue and assign to the CTO for review.
# Using production
SSO is enabled for all @flowfuse.com employees. Everyone is a member of FlowForge Team
where Applications/Instances can be created.
By default, FlowFuse employee accounts do not have Admin level access. A dedicated admin account exists with details in 1Password for those with approved admin level access.
If you want to create your own Team for work purposes, use your Brex card when setting up the billing details. You can then request a Stripe Coupon to cover the costs by raising an issue in CloudProject
# Deployment to FlowFuse Cloud
Any pull requests that are merged into main will automatically trigger a deployment to the production environment. As such, it is vitally important that PR Reviews are conducted thoroughly, following our guidance here.
All pull requests can be tested in a full staging environment ahead of being merged. Details on how to do this can be found in our Contributing guide.
# Observability
- Observability - how we monitor production