Skip to content

About

Independent open-source Teamily alternative: management server and FlyBot runtime containers

Resources

Stars

1 star

Watchers

0 watching

Forks

 
 

Repository files navigation

OpenTeamily

An independent, open-source, self-hostable project targeting full Teamily feature parity. This is a new project under the openTeamily organization, not a continuation of development in the original FlyBot repository.

OpenTeamily is a project name, not a claim of affiliation with or endorsement by Teamily. Final product branding remains open; no proprietary code, logos, fonts or legal text are included.

Status

Current slice: a runnable Python/SQLite authentication, workspace, and simulated instance/jobs API; an opt-in operator Compose execution CLI (default disabled) with HTTP/subprocess-stub tests; and a first, minimal source import of related FlyBot and Bot Social trees. Live Docker/FlyBot/real-volume acceptance, management integration of the imported trees, and browser workflows remain unverified or missing. See operator setup, recovery, evidence limits and next tasks, lifecycle scope and remaining gates, and implemented routes, startup/test commands, security configuration and gaps. Older FlyBot tests, screenshots and PRs do not establish functionality in this repository.

Agent runtime baseline: the runtime tracks upstream DS Bot's latest release, currently v0.3.8, pinned in runtime/ds-bot-upstream.pin.json. CI checks that the vendored tree is unmodified, runs upstream's own suite on the DSH version the pin names, and runs upstream's container startup test. A daily workflow opens a pull request when a newer upstream release exists. See runtime/ds-bot-upstream/UPSTREAM.md.

Architecture

  • Management server: accounts, authentication, workspaces, permissions and container lifecycle.
  • FlyBot runtime containers: execute Agents and expose an authenticated runtime adapter contract.
  • Both layers must be open-source and self-hostable. The first optional runtime adapter uses local Compose with independent instance IDs; final user/workspace allocation granularity is not decided.
  • FlyBot customization (the social plugin and instance docker helpers) and Bot Social protocol source are imported as isolated snapshots under runtime/flybot and services/bot-social; they keep their original licenses and are not relicensed as OpenTeamily MIT. This tree does not vendor the old FlyBot core/ fork. The runtime baseline is the pinned upstream DS-Bot v0.3.8 tree under runtime/ds-bot-upstream. The management server is not yet wired to those trees. See migration notes, gaps and licensing.

Next steps

  1. Review the architecture and full capability map.
  2. Create native issues/subissues in this repository, including dependencies and observable acceptance criteria.
  3. Review the authentication/workspace foundation, then deliver durable runtime jobs and the fake backend; review the opt-in manager/Compose adapter, then perform separately approved real container and Teamily comparison acceptance.

See architecture, capability roadmap and reuse policy.

License

New material authored in this repository is licensed under MIT; see LICENSE. This does not relicense any FlyBot, Bot Social, runtime or third-party material.

Imported FlyBot customization source remains Apache-2.0 with its NOTICE. Imported Bot Social source remains MIT, Copyright (c) 2026 Birfy. runtime/ds-bot-upstream/ is an unmodified, pinned copy of upstream DS Bot under the Apache License 2.0 (its LICENSE and NOTICE are kept there). No upstream git history is imported. See docs/LICENSING.md and runtime/ds-bot-upstream/UPSTREAM.md.

About

Independent open-source Teamily alternative: management server and FlyBot runtime containers

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages