Cultivate Your Builds
Build Orchestration — Reimagined
An enterprise-grade, event-driven build orchestration that grows with you.
Your data never leaves your infrastructure. Powered by Rust.
Build Systems, Naturally
Farmland borrows the language of agriculture to make complex build orchestration intuitive. Every concept maps to something you already understand.
Farmfile
Build ConfigurationYour crops start with the recipe. A farmfile defines operations on a field — what to build, which variants to use, and how dependencies connect — in a clean, readable format.
[operation.build]
variant: release
work: cargo build --release
after: prepareParcel
Build ArchiveThe harvest of your build. After a target runs, its output is archived into a parcel — a content-addressed package stored on S3-compatible object storage. You get a hash, and anyone can download the result.
# after target completes
parcel: build-output/
→ sha256:a3f8c1... ✓ uploadedBuddy
Control Plane AgentYour farmhand on-site. Buddy runs in your infrastructure — your source code and build data never leave your house. Unlike other CI/CD SaaS tools, nothing gets uploaded to someone else's cloud. Logs are encrypted with your public key before leaving the agent. Only you can decrypt them.
[buddy]
plugin: parcel
plugin: git-watcher
# 🔒 logs encrypted with your pubkey
# 📦 data stays in your infraFarmland Cloud
SaaS PlatformThe sky above your fields. Farmland Cloud orchestrates build events via NATS and provides dashboards and team collaboration — but never sees your source code or build output. Logs arrive encrypted with your public key. We cannot read them. Your data, your keys, your control.
buddy 🔒→ Farmland Cloud
↳ NATS event bus (TLS)
↳ logs: pubkey-encrypted
↳ source code: never leaves youFrom Seed to Harvest
Four simple steps from configuration to deployed artifacts.
Define
Write Your Farmfile
Start by describing your build in a simple, readable config. Define operations on a field — variants, dependencies, and work commands — Farmland understands them all. Just write it down, and you're ready to farm. No more scripting your build logic in opaque CI YAML or wrestling with Makefiles.
Execute
Buddy Takes Over
Trigger a build and Buddy — your local control plane — resolves dependencies, runs operations, and streams events to Farmland Cloud. Its blazingly fast and reliable so your builds finish with less overhead. Watch the magic happen in real-time, and let Buddy handle the heavy lifting.
Archive
Parcel Your Output
After a target completes, the parcel plugin kicks in — archiving your build output into a content-addressed package and uploading it to a store. You get a hash, and anyone can download it without a hassle.
Harvest
Download & Share
Any parcel can be retrieved by its hash. Share build output across teams, CI pipelines, or environments — just pass the hash and download from your object storage. Pass it for the next machine to consume, or download and inspect locally with the help of a VS Code extension. It's that easy.
Meet Buddy Agent
The heart of Farmland runs in your infrastructure — not in our cloud. Buddy is the control plane agent that coordinates everything locally.
Runs in Your House
Buddy runs on-premise in your infrastructure. Not in Farmland Cloud. Not in any cloud. Your machines, your network, your control. This is the critical distinction from other CI/CD SaaS solutions.
Event Coordination Hub
Buddy handles all event orchestration — receiving triggers, coordinating workflows, managing plugins, and streaming status back to Farmland Cloud. It's the central nervous system of your builds.
Extensible Plugin System
Extend Buddy with plugins — parcel archiving, git watchers, notification hooks, and custom integrations. The plugin architecture lets you adapt Buddy to your exact workflow.
Going Open Source
Buddy will be open-sourced. Inspect every line, audit the code, extend it freely. No black boxes running in your infrastructure.
The Farm Runner
A standalone, isolated binary that executes your builds. Your commands never leave your repo.
Farmland Never Sees Your Commands
The farmfile lives in your repository. We only see symbolic target names — never the actual shell commands or environment variables.
Going Open Source
Farm Runner will be open-sourced. Audit the execution engine yourself. No mystery binaries running your builds.
Standalone & Isolated
Farm Runner is a standalone binary, completely isolated from Buddy. It parses your farmfile locally and executes the actual work. No network calls to Farmland for command execution.
Recipe Lives in Your Repo
The farmfile — your build recipe — is checked into your repository. Not stored in Farmland Cloud. Version-controlled alongside your code, reviewed in your PRs.
No Environment Injection
Only symbolic targets can be triggered from the cloud. No ability to inject environment variables or modify commands remotely. What's in your farmfile is what runs — nothing more.
Hidden Behind Parsing
Commands are hidden behind the parsed farmfile structure. Farmland Cloud sees the shape of your build graph, not the contents of your scripts.
Farmland Cloud
Coordination and orchestration — not remote execution. A fundamentally different approach to CI/CD SaaS.
Not a Remote Runner
Most CI/CD SaaS platforms are remote runners — your builds execute on their machines, with your source code, secrets, and environment variables exposed to their infrastructure.
Farmland Cloud is purely an orchestration layer. Builds run in your infrastructure via Buddy. The cloud coordinates events and provides dashboards — that's it.
Event-Based Coordination
All communication happens via CloudEvents over NATS. Build triggers, status updates, completion notices — pure event streaming. No RPC calls executing commands.
Dashboards & Monitoring
Real-time build monitoring, team dashboards, historical analytics. See what's running, what succeeded, what failed — without exposing your actual build logic.
Team Collaboration
Shared workspaces, access controls, notification routing. Coordinate your team's builds without centralizing your infrastructure or exposing sensitive data.
Why This Matters: Clean Separation
Because execution is completely decoupled from coordination, script complexity and environment variable chaos cannot creep into the control plane.
This is a fundamental architectural distinction from other CI/CD SaaS solutions. Your build complexity stays in your repo. The orchestration layer stays clean. Security boundaries are enforced by design, not policy.
Built-in Security by Design
Not an afterthought. Security is architected into every layer of Farmland — from connection to logs to execution isolation.
Encrypted Build Logs
Your logs. Your keys. We literally cannot read them.
Build logs are encrypted with your public key before leaving the Buddy agent. When logs arrive at Farmland Cloud, they're already ciphertext. Only you hold the private key to decrypt them.
Secure Buddy Connection
TLS encryption with credential-based authentication.
Buddy connects to Farmland Cloud over TLS-encrypted NATS. Authentication uses credential files that you control. No shared secrets stored in our infrastructure. Connection is outbound-only from your network.
Source Code Isolation
Your source code never leaves your infrastructure. Farm Runner executes locally. No code upload to any cloud service.
Secrets Stay Local
Environment variables and secrets are defined in your farmfile, in your repo. Never transmitted to Farmland Cloud.
Complete Audit Trail
Every event is logged and timestamped. Track who triggered what, when, and from where — all without exposing build contents.
Security isn't a feature toggle. It's the architecture. With Farmland, data sovereignty and privacy aren't compliance checkboxes — they're structural guarantees.
Why Teams Switch to Farmland
Enterprise CI/CD costs spiral out of control. Farmland changes the economics by running builds on your infrastructure while eliminating the complexity that drives those costs.
No Config Drift
The farmfile lives in your repository. When a developer runs `farm build`, they execute exactly what CI executes. Same commands. Same environment. Same results. No more "works on my machine" because local and CI are the same machine logic.
No Complexity Creep In
Traditional CI becomes a tangled mess of YAML, scripts, and hidden logic. With Farmland, CI is pure orchestration — it only sends symbolic events like "run build:release". The actual build logic stays in your farmfile. Clean separation. No script spaghetti.
Zero CI Compute Costs
Traditional CI/CD charges per-minute for cloud compute. GitHub Actions, CircleCI, GitLab — they all bill for CPU time. With Farmland, builds run on your infrastructure. Your existing machines. Zero per-minute charges. Zero egress fees. Zero control plane costs.
Typical enterprise with 10,000 builds/month: CI costs of $4,800-$9,600/month become $0 with Farmland — plus faster debugging and zero environment drift.
Calculate Your SavingsEverything You Need to Build at Scale
Enterprise-grade capabilities that scale from single projects to massive monorepos.
Event-Driven Architecture
Built on NATS messaging for real-time, distributed event processing. Every build operation emits CloudEvents that flow through the system — enabling live monitoring and seamless scaling across your infrastructure.
- CloudEvents specification
- NATS-based messaging
- Real-time build monitoring
- Distributed event replay
Your Data Never Leaves Home
Unlike other CI/CD SaaS platforms, Farmland never touches your source code or build output. Buddy runs locally in your infrastructure. Logs are encrypted with your public key before transmission — Farmland cannot read them, ever.
- Source code stays on your infra
- Logs encrypted with your pubkey
- Farmland has zero access
- No sources uploaded to our cloud
Variant System
Build the same project in multiple configurations from a single source. Debug, release, cross-platform — define variants once and Farmland handles the specialization and matrix execution.
- Multi-variant builds
- Matrix execution
- Variant-specific overrides
- Cross-platform support
Buddy Plugin System
Buddy is the local control plane that connects to Farmland Cloud. Extend it with plugins — parcel archiving, git watchers, notifications, and more. Build your own plugins for custom workflows.
- Parcel archiving plugin
- Git watcher plugin
- Notification plugins
- Build your own plugins
Parcel Archives & Storage
After a target runs, output is archived into a content-addressed parcel and uploaded to a store. Retrieve any artifact by its hash — no duplication, no confusion.
- Hash-based deduplication
- Cross-team caching
- Incremental storage
- Artifact streaming
VSCode Integration
First-class editor support with syntax highlighting for farmfiles, inline build status, and one-click execution. Farmland lives where you code — not in a separate dashboard.
- Farmfile syntax highlighting
- Inline build status
- Quick run actions
- Error navigation
Plant Your First Seed
Sign up for early access and be among the first to experience Farmland.
Open Source + SaaS
Farmland is open source at its core with optional SaaS features.
Support development or upgrade when you're ready.
Support Development
Your contribution helps us maintain and expand Farmland.
Thank you for being part of our community!
🔒Secure payment powered by Stripe. We never see your card details.