Reference/Repositories

Repositories

Ether is a multi-repo product. Integrators usually touch API + SDK + their own harness repo.

Platform

ether-core

Backend monorepo: ether-api, harness service, domain logic, migrations, @ether/os-sdk.

• Run API locally: ether-core/run_api.sh or LUMA_API_BIND=127.0.0.1:8080
• Deploy: make ether-api-deploy from ether-core (see docs/env-setup.md)

ether-app

Product frontend at app.tryether.ai (AWS Amplify). Submits tasks, subscribes to realtime, renders delivery.

Env: NEXT_PUBLIC_ETHER_API_BASE_URL=https://api.tryether.ai

Integration

ether-code

Reference external coding harness. Depends only on @ether/os-sdk.

npm run worker -- run <task_id>   # pull
npm run worker -- serve           # push stub

ether-docs

This documentation site. Deploy static build to docs.tryether.ai (recommended).

landing

Marketing site for tryether.ai.

What to fork vs what to depend on

Build…	Start from…
Custom coding agent	Fork or copy ether-code patterns
Custom UI	ether-app or your stack + Product + Realtime APIs
Docs for your product	Fork ether-docs VitePress site

Do not fork ether-core to ship a harness — stay on HTTP/SDK.

Links

Surface	URL
API	https://api.tryether.ai
App	https://app.tryether.ai
Marketing	https://tryether.ai
Docs (this site)	https://docs.tryether.ai (after deploy)