---
title: "Operations"
description: "This covers how we run our business and deliver service to our customers."
canonical_url: "https://flowfuse.com/handbook/operations/"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# Operations

This covers how we run our business and deliver service to our customers.

- [Data](https://flowfuse.com/handbook/operations/data)
- [Billing](https://flowfuse.com/handbook/operations/billing)
- [Accounts](https://flowfuse.com/handbook/operations/accounts)
- [Change Control](https://flowfuse.com/handbook/operations/change)
- [Vendors](https://flowfuse.com/handbook/operations/vendors)
- [Insurance](https://drive.google.com/drive/folders/1Q2UqEmusDIpBD4-4Km1eFksHaRkVzl7O?usp=drive_link)

### Services used at FlowFuse

At FlowFuse there's a couple of services that are vital to the operation of the
business. As a matter of having a plan before these services are taken offline
or go bankrupt a table is maintained with where to go in case of service disruption.

<table>
<thead>
  <tr>
    <th>
      Primary service
    </th>
    
    <th>
      Goal
    </th>
    
    <th>
      Backup Service
    </th>
    
    <th>
      Do not use
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Slack
    </td>
    
    <td>
      Emphemeral internal communication
    </td>
    
    <td>
      Google Spaces (in Gmail)
    </td>
    
    <td>
      Email (only for legal items)
    </td>
  </tr>
  
  <tr>
    <td>
      Slack Huddles
    </td>
    
    <td>
      Internal face to face commuication
    </td>
    
    <td>
      Google Meet
    </td>
    
    <td>
      -
    </td>
  </tr>
  
  <tr>
    <td>
      Google Meet / Zoom
    </td>
    
    <td>
      External video calls
    </td>
    
    <td>
      Google Meet / Zoom
    </td>
    
    <td>
      -
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://support.google.com/calendar/answer/10729749?hl=en" rel="nofollow">
        Google Appointment Schedules
      </a>
    </td>
    
    <td>
      Scheduling meetings with external parties
    </td>
    
    <td>
      Calendly
    </td>
    
    <td>
      -
    </td>
  </tr>
  
  <tr>
    <td>
      AWS
    </td>
    
    <td>
      Hosting for FlowFuse Cloud
    </td>
    
    <td>
      ?
    </td>
    
    <td>
      -
    </td>
  </tr>
  
  <tr>
    <td>
      GitHub
    </td>
    
    <td>
      Task management, planning and code development
    </td>
    
    <td>
      -
    </td>
    
    <td>
      -
    </td>
  </tr>
</tbody>
</table>

## Calendar Conventions

To help team members quickly identify meeting types in calendar apps and menubar tools, use these emoji conventions when creating calendar entries:

- 🎥 - Google Meet meetings (add this emoji to the event title for quick visual identification)

This convention is particularly helpful for:

- Quick visual scanning in menubar calendar apps
- Distinguishing Google Meet from Slack Huddles at a glance
- Identifying external-facing meetings quickly

**Note:** For internal face-to-face discussions, prefer Slack Huddles in public channels over Google Meet when possible, as noted in the services table above.

## Mail Handling

FlowFuse uses [Earthclass Mail](https://www.earthclassmail.com/) to handle physical mail. Earthclass Mail receives all incoming mail on our behalf, scans it, and makes it available digitally. By default, physical mail is shredded after scanning — if a piece of mail needs to be retained physically, shredding must be cancelled before it occurs. Any checks that need to be cashed cannot be processed automatically and must be handled manually; the CEO typically takes care of this.

## Email

While there are a number of email aliases and google groups used throughout the organization, there is some activities across operations, people operations, and finance management that requires that activities be done with external parties. As a redundancy, rather than use a person's individual email (e.g. the CEO's own address), we use a google group to avoid the risk of information getting lost. For example, for some government filings, we use ops@.

## GitHub

We use GitHub for task management, planning and code development across the company. The following is a high-level guide to the core repositories.

The Engineering team maintains a large number of repositories related to individual components of the product.

<table>
<thead>
  <tr>
    <th>
      Repository
    </th>
    
    <th>
      Purpose
    </th>
    
    <th>
      Public/Private
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      FlowFuse/admin
    </td>
    
    <td>
      Company Admin tasks; onboarding/offboarding employees, access requests, release checklists
    </td>
    
    <td>
      private
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/website
    </td>
    
    <td>
      The FlowFuse Website, including handbook
    </td>
    
    <td>
      public
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/CloudProject
    </td>
    
    <td>
      Task management for FlowFuse Cloud platform
    </td>
    
    <td>
      private
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/marketing
    </td>
    
    <td>
      Task management for events and customer-specific work; webinars, artwork requests
    </td>
    
    <td>
      private
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/dev-env
    </td>
    
    <td>
      FlowFuse development environment tooling
    </td>
    
    <td>
      public
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/flowfuse
    </td>
    
    <td>
      The core product code repository
    </td>
    
    <td>
      public
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/product
    </td>
    
    <td>
      A higher level planning and strategising repository for FlowFuse
    </td>
    
    <td>
      private
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse/node-red
    </td>
    
    <td>
      A planning repository for upstream Node-RED tasks
    </td>
    
    <td>
      private
    </td>
  </tr>
</tbody>
</table>

To create a new repository, first open an issue in the [Admin](https://github.com/FlowFuse/admin) repository using the New Repository checklist. This ensures all required security controls are applied.

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
