LogoLogo
HomepageCommunitySign Up
  • Introduction
  • Values
  • Product
    • Weekly Product Meeting
    • Development Process
    • Writing Specs
    • Fast-Track Changes
    • Technology Stack
    • Checklist for New Features
    • Translation
    • Environments
    • Testing
    • Monitoring
  • Growth
    • The Importance of Customers
    • Copywriting
    • Ideal Customer Profile
    • Value Proposition
    • Sales Funnel
      • Introduction
      • Discovery Calls
      • Demos
      • Conversion Rates
    • Website
      • Website Sitemap
      • SEO
      • Product Screenshots
    • Partner Program
    • Rewards Program
    • Customer Logos
    • Competitor Benchmarking
    • Writing Cold Emails
  • Customer Success
    • Product Analytics
    • Reported Issues
    • Admin Backend
    • Stripe Management
    • Extending Free Trials
    • Writing Documentation
    • Feature List
  • People
    • Hiring
    • Onboarding
    • Offboarding
    • Employee Stock Option Programme
  • Operations
    • Writing SOPs
    • Free Cash Flow Tracking
    • Banking
  • Brand Assets
Powered by GitBook
On this page
  • 1. Development
  • 2. Beta
  • 3. Production

Was this helpful?

  1. Product

Environments

PreviousTranslationNextTesting

Last updated 1 year ago

Was this helpful?

Blue has three main environments:

1. Development

is the bleeding edge, often with breaking changes and has a unique database instance. This contains all the latest in-progress features. Used by Blue team to test for changes, and by customers who are interested in trying things out.

While we encourage customers to try our Blue Development Environment to see new features, make sure that you do not use it for real work, as we regularly refresh and wipe the data on this environment.

2. Beta

is our public Beta program. It has features that are currently in Beta testing, but it shares the database with the production environment. It has a fraction of the infrastructure resources of the production environment. This means that any customer can log in and use Beta. The data that they have in the production environment will be shown, and any changes they make will automatically sync in the production environment.

Features typically live in Beta for 4-6 weeks before being released into production. This ensures that we have meaningful statistics on stability and usage. This is important because, in our opinion, stability is itself a feature.

3. Production

The is our main version of Blue, where we optimize for stability and uptime.

The Blue Development Environment
Blue Beta
Blue Production Environment