How Colony Core Works

Request beta access, complete the verification steps, and start onboarding once your workspace is approved. Colony Core is working toward open beta, but current access is still reviewed.

Request Beta Access See pricing

Four Steps to Getting Started in Beta

1. Request Beta Access

Create your account request through the beta signup flow. Current onboarding does not require a sales call.

2. Accept Terms and Verify Email

Complete the legal acceptance flow and verify your email address. Beta access requests remain pending until those steps are complete.

3. Wait for Approval

Once approved, sign in and set up the workflows you want to start with first. Jobs, flight logs, and equipment tracking are typical starting points.

4. Run Your First Workflow

Create a job, log a flight, and generate an invoice. Billing status tracking is available now, with selected payment workflows enabled only in supported beta setups.

What Happens Automatically

Colony Core connects your operational data without extra steps. As you work, the system keeps records consistent and linked across modules:

Flight hours accumulate against aircraft records automatically when you log flights.
Maintenance alerts trigger when equipment reaches service intervals based on actual usage data.
Billing status can update on jobs and invoices when supported payment workflows are enabled.
Operational records stay linked so jobs, flight logs, equipment, and invoices keep shared context.
Equipment availability reflects current maintenance status when you assign aircraft to jobs.

For the full list of automatic and user-initiated actions, see Integrations and Data Flow.

Set Up at Your Own Pace

Start Here (Day 1)

Create your first job
Log your first flight
Generate your first invoice

This is all you need to get value from Colony Core.

Add When Ready

Register equipment for maintenance tracking
Import historical jobs via CSV
Use standard exports for accounting workflows
Advanced integrations coming soon
Invite team members

Typical Time to First Value

Most approved operators can begin onboarding in their first session. Exact time to value depends on approval timing, migration needs, and which workflows you decide to start with first.

Same day

Access request, legal acceptance, and verification

First session

Initial setup for jobs, teams, and records after approval

First week

First live workflow completed in the beta environment

Support When You Want It

Help is available during beta when you want guidance or need to confirm whether a workflow is currently supported:

Getting Started guide walks through your first job end-to-end.
Help Center covers every feature with step-by-step instructions.
Support team can handle onboarding, privacy, security, and beta availability questions.

Support is optional, but beta rollout questions are expected. Use it when you need current availability confirmed.

What You Can Expect

Beta access requests are reviewed before first login.
You can start with a narrow workflow and expand later.
Automation is available where configured, with more workflows rolling out over time.
Data import and export are available for selected workflows.
Advanced integrations remain beta-limited.
Security practices and privacy controls are documented conservatively.

Ready to Start?

Request beta access, complete verification, and we’ll follow up as onboarding expands toward open beta.

Request Beta Access Explore features Calculate your ROI