Everdone
Everdone offers AI services for code documentation, engineering review and QA. Its official site lists CodeDoc, CodeReview, CodeSecurity, CodePerformance and TestCase as live services. Teams can evaluate one service or use several around a repository and its requirements.
Documentation and tracked reviews
CodeDoc connects to GitHub and generates documentation for selected repositories, folders or files. The publisher describes updates as the code changes. Check an explanation against the underlying file before relying on it for onboarding or a design decision.
CodeReview accepts pull requests, branches or files and produces findings with suggested fixes. The shared workflow includes issue assignment, status tracking and re-review. That record can help a team follow a concern through a proposed fix, but a repeated AI pass is not independent proof that the change is safe.
Security and performance have separate review services. Their descriptions include risk or impact classification, explanations and fix tracking. Treat a security finding as a hypothesis to reproduce and a performance claim as something to measure under the actual workload. The site's promise of finding real risks does not establish complete vulnerability coverage.
Requirements into test cases
TestCase accepts requirements, screenshots or a feature description and generates structured scenarios. The pricing description lists assignment, filtering, status tracking and Excel export of a summary and full test suite.
This is test-case generation, not evidence that the application has passed those tests. Review the expected outcomes and add cases for the product's own permissions, data and error paths before execution. A screenshot can supply interface context while leaving business rules unstated.
The site marks database documentation and changelog generation as coming next. Those should not be assumed to be part of the live toolkit.
Usage units and evaluation
Everdone describes usage-based charges with unlimited team access rather than per-user seats. Documentation uses files documented as the unit; review services use files per review. TestCase charges per generated test case. The pricing page states that re-reviews are charged for files reviewed again, so iterative verification can add usage.
Free starting allowances are displayed per service, with promotional early-access prices. Confirm the current rate and unit definition before estimating a recurring workflow. Public demos and claims of production-ready output are publisher evidence, not measured results for your repository. Evaluate a bounded set of files or requirements, inspect the result, and preserve your own engineering and QA acceptance checks.