# Get started: Ready from day zero

Canonical: https://fairleadhq.com/get-started/

Updated: 2026-09-22
Publication state: published
Product version: platform

Agent summary: Getting started with Fairlead: connect a repository and optionally secure connectivity, and results begin. Enterprise engagements run a five phase pilot over roughly six to eight weeks to a go or no-go decision. The connector is outbound only, identity aware, isolated per customer and fully logged.

## Prerequisites

- None declared.

## Inputs

- None declared.

## Outputs

- None declared.

## Limitations

- None declared.

## Permissions

- None declared.

## Privacy

- None declared.


Fairlead is production ready out of the box. Connect your repository, and set up secure connectivity if your environment needs it, and your first tests and fixes start landing. No lengthy implementation, no infrastructure to stand up.

## How you start

On a standard stack it takes four steps. Complex, regulated or legacy environments add a structured pilot.

1. Join the waitlist: Leave your work email and a line about your stack. We write when there is a place for you.
2. Connect your repository: Connect repositories and your tracker over OAuth 2.0 or an API token. Cloud hosted tools need no network level access.
3. Set up secure connectivity, if you need it: For on-premise or private environments, a connector inside your network dials out. Nothing inbound is opened on your side.
4. Your first tests and fixes land: They arrive as pull requests into your repository.

## A pilot shaped around your needs

Every app and team works a little differently. When your workflow, codebase or requirements need extra care, we work with you through a hands-on pilot to adapt Fairlead and assess the results together before a wider rollout.

The timeline below is for teams that need a tailored pilot. If you're ready to connect and start, you can get going without one.

### Alignment (About a week)

- Agree scope and success criteria
- Capture code style and standards
- Map test frameworks and CI/CD
- Review legacy systems and constraints

### Connect (About a week)

- Connect repositories and trackers
- Set up secure connectivity, if required
- Configure for your stack
- Onboard the pilot team

### Tuning (Two to three weeks)

- Run bug fixing and test generation cycles
- Review results with the team
- Tune the quality of what comes back
- Iterate until the criteria are met

### Go or no-go (About a week)

- Evaluate the pilot results
- Reach the decision point
- Formalise the operating model
- Define responsibilities

### Scale up (Ongoing)

- Extend to more teams
- Start a community of practice
- Establish governance
- Monitor coverage and return

## How we connect, without opening a port

A connector inside your environment dials out. Nothing dials in. Every request from Fairlead is checked against identity and policy at the edge before it reaches a service of yours.

### Your environment

- No open ports: The connector dials out to the edge. Nothing inbound is opened on your side, so no public IPs and no firewall changes.
- Private connectivity: Reach internal services over TCP, UDP and ICMP. Map specific hostnames or IP ranges, so only what you expose is reachable.

### Zero Trust edge

- Identity aware: Every request is authenticated and authorised against identity, device posture and network context before it reaches a service.
- Isolated per customer: A separate account for each customer keeps tenants apart, with governance and policy scoped to one environment.
- Fully logged: Access policies, identity checks and gateway events are logged end to end, for a reviewable audit trail.

## Built to run securely

Fairlead is a managed service. There is no infrastructure to provision or maintain on your side, and the compute that does the work runs on ours.

- Integration (OAuth 2.0, API token): Connect repositories and work management tools over OAuth 2.0 or an API token. No network level access is needed for cloud hosted tools.
- Secure connectivity (TLS tunnel, IP allow list, VPN peering): For on-premise or private environments, an outbound-only TLS tunnel agent, static IP allow listing, or VPN peering.
- Data security (TLS 1.2+, AES-256): Encrypted in transit at TLS 1.2 or better and at rest with AES-256. Source is read only and is not stored beyond the processing window.
- Access control (SAML, OIDC, RBAC, Audit log): Single sign on over SAML or OIDC, role based access control (RBAC), and full audit logging. Each customer environment is isolated.

## What we support today

Where a connector or a language is not listed, say so. We build them in the order people ask for them.

- Languages: Java and Python today. C#, JavaScript, TypeScript, Rust and Go are on the way. The logic is built per language rather than generated by a general purpose assistant.
- Version control: GitHub, GitLab, Azure DevOps and Bitbucket, cloud or on-premise.
- Task tracking: Jira and GitHub Issues.
- Models: Model agnostic across the major providers. Your data is never used for training or fine tuning.