Frequently asked questions

No. FlyDocs enforces your workflow and syncs project metadata between your developers' coding tools and your project management tool. Your code stays in your coding environment and your version control system. FlyDocs does not read, store, or transmit your source code.

Provider credentials (Linear, Jira) are encrypted at rest with AES-256-GCM and only decrypted in memory for the duration of a single relay request. FlyDocs API keys are stored as SHA-256 hashes; the plaintext only ever exists on the developer's machine. We store workspace configuration, generated context (project.md, service descriptors), and usage metadata. We do not store source code, git history, or relay request and response bodies.

FlyDocs works with Cursor, Claude Code, Windsurf, Warp, and Codex today. Support for additional tools is on the roadmap. Contact us at support@flydocs.ai if your team uses a different tool.

Minimally. Developers install FlyDocs in one command and most of what it does runs automatically from there. Code checks run in the background, project tickets update on their own, and context loads before every AI interaction. The main change is using simple commands inside their coding environment to move tasks through stages rather than switching to a browser to update a ticket manually.

A configuration file is a starting point. FlyDocs is a workflow system built for teams. Configuration files drift because every developer edits their own copy. FlyDocs manages configuration centrally so every developer always runs the same setup. Configuration files do not enforce anything. FlyDocs enforcement runs unconditionally and cannot be bypassed. Configuration files do not sync to your issue tracker, do not carry session memory, and do not give you one-command onboarding for new developers.

Linear and Jira are supported today with live two-way sync. GitHub Issues, Asana, ClickUp, Notion, and Trello are on the roadmap. On the Free plan, FlyDocs uses local file-based task tracking that works without any PM tool connection. Contact us at support@flydocs.ai if your team uses a different tool that isn't planned on the current roadmap.

Your workspace configuration and project data can be exported before you cancel. We will give you adequate notice of any service changes and your data is never deleted without your consent.