ecko
Commercial licence
Effective 16 August 2026 · applies to v0.34.0
Free to learn.
Licensed to ship.
Evaluate Ecko on your own hardware, against your real workloads, for as long as you need. When it goes into production you licence the developers who write it, and nothing about the software changes.
$189
per developer, per year
Refunded in full within 14 days. No key to enter, no account to create.
Who pays
Does your company need a licence?
Free
- Learning the language, and teaching it
- Side projects and anything not commercial
- Evaluating on company hardware, against your real workloads
- No time limit, no key, no registration
Personal, educational and evaluation use, as set out in the EULA.
Needs a commercial licence
- Running in production
- Internal tooling the business depends on
- Anything shipped to customers
- One seat per developer who writes or edits Ecko
Business use, as set out in the commercial licence.
A seat is a person, not a machine. One licence for each developer who writes or edits Ecko code. Build agents, test runners and deploy pipelines are not seats, and neither is an operator running a service that happens to be written in Ecko.
What changes
A licence changes one thing
Your company is allowed to run Ecko commercially. The software is the same software.
No key, no account
Nothing to enter and nothing to activate. The binary carries no licence check, so a licence takes effect when payment clears and the file on your machines is the same file it was before.
No telemetry
No analytics, no update ping, no usage reporting. Nothing about your code or your machines is sent anywhere.
Nothing stops if it lapses
Anything already deployed keeps running. There is no kill switch and no phone home, so a lapsed licence is a billing problem and never an outage.
What it costs
Two ways to buy
Team
$189 per developer, per year
For a team putting Ecko into production.
- Commercial use, in production and in anything you ship
- Email support, answered within one business day
- Security advisories before they are made public
Refunded in full within 14 days.
Enterprise
Custom quoted per organisation
For a deployment too large to count in seats, or a procurement process that needs its own paperwork. Everything in Team, plus:
- A site licence covering every developer, on one invoice
- A named contact, and onboarding for the first team
- Custom terms, on your paper or ours
- Answers to your security questionnaire, in writing
- Purchase orders and invoicing outside Paddle
- Source access where procurement requires it
- Input on the roadmap, and notice of breaking changes before release
Due diligence
The security review, answered in public
The questions a company asks before it adopts a tool from a small vendor. The usual answer is a form and a two week wait, so they are answered here instead. There is no SOC 2 report and no auditor: these are the answers themselves, each linked to the document that governs it, and each with a reference you can quote in a questionnaire.
The product, and your data6 answers
- Disclosure E-01 Licence enforcement
- None. No key to enter, no account to activate, no licence check in the binary. EULA
- Disclosure E-02 Telemetry in the binary
- None. No analytics, no update ping, no usage reporting. Nothing about your code or your machines is sent anywhere. This website is separate; see the privacy answer two rows down. Privacy
- Disclosure E-03 Network egress
- Only the requests your own program makes. Without a provider key it runs in mock mode and makes none at all. Privacy
- Disclosure E-04 Data we hold
- The name and email on the licence, the company, the plan and the payment status. Card details never reach us. Privacy
- Disclosure E-05 Third-party code on this site
- Two origins. Google Analytics on every page, and Paddle's checkout script only when you press a buy button. No advertising, no external fonts. Neither runs inside the product. Privacy
- Disclosure E-06 Dependency provenance
- Packages are vendored into your own repository and pinned by sha256 in
ecko.sum. Nothing resolves at build time. Manifests
Running it, and support6 answers
- Disclosure E-07 Continuity
- Anything already deployed keeps running if a licence lapses. No kill switch, no phone home. Refunds
- Disclosure E-08 Source access
- Not generally. Ecko ships as prebuilt binaries. Source access can form part of an enterprise agreement where procurement requires it.
- Disclosure E-09 Supported platforms
- Linux x86-64 and arm64, macOS arm64, Windows x86-64. One binary, no runtime to install alongside it. Downloads
- Disclosure E-10 Security reports
- security@ecko.sh, acknowledged within one business day.
- Disclosure E-11 Advisories
- Licensed customers are told about security advisories before they are made public.
- Disclosure E-12 Support
- Email, answered within one business day, on Team and above.
Commercial and legal4 answers
- Disclosure E-13 Tax and invoicing
- Paddle is the merchant of record, is the seller named on your invoice, and collects any local sales tax or VAT at checkout. Terms
- Disclosure E-14 Refunds
- Fourteen days from a first charge, in full, with no survey. Refunds
- Disclosure E-15 Governing law
- The laws of the jurisdiction in which Machine Republic (Pty) Ltd is established. Terms
- Disclosure E-16 Notice of change
- At least 30 days by email before a material change to the terms takes effect for existing customers. Terms
- Vendor
- Machine Republic (Pty) Ltd
- Seller of record
- Paddle
- Licence
- Proprietary, per developer
- Currency
- US dollars
Licence your team
$189 per developer per year, billed annually. Cancel from your Paddle receipt at any time. The plan comparison and the licensing FAQ cover what each plan includes.