Skip to content
Appvecta

Editions

Community is not a trial.

Brain features will never require an AI provider or an Appvecta account. Without an account no licence server is contacted and nothing local is disabled. Edition names are working titles and pricing is not finalised.

Community

Free forever

Free · Targeted for the private alpha

Everything local. Community is not a trial: Brain features never require an AI provider or an Appvecta account, and nothing local is disabled without one.

  • Appvecta Brain — the full project graph, architecture map and trace
  • Impact analysis
  • Run, Device Hub and QA
  • The local MCP server
  • Your own API keys, or a local Ollama model
  • No account, no network, no licence check
  • It never degrades offline

Team

Pricing not finalised · Post-alpha

For a team that wants shared understanding without putting source on a server.

  • Shared organisation and project graphs
  • Live overlays and conflict warnings when two people touch the same node
  • Team knowledge
  • The admin web console
  • Token reports per project, team and developer, against a baseline
  • By default the server receives graph facts — names, kinds, edges, ranges, hashes — not source code

Knowledge Hub

Add-on · pricing not finalised · Post-alpha

The documents around the code, answerable in the same place as the code.

  • A per-project document store for specs, API docs, designs and notes
  • Document Q&A with citations, through MCP and in the IDE

Chat

Add-on · pricing not finalised · Post-alpha

For people who would rather not configure a provider at all.

  • Appvecta-hosted models in the IDE chat
  • No MCP setup and no API key

Enterprise

Pricing not finalised · Post-alpha

Cross-project impact and the controls a larger organisation needs.

  • Project merge and cross-project impact
  • SSO and SCIM
  • Audit export
  • Data residency
  • A self-hosted server and air-gapped mode

Pricing is not finalised. No figure on this site should be read as a price, because there are none.

Benefits

What each group is meant to get out of it.

Every row pairs a benefit with the mechanism that would produce it — because a benefit without a mechanism is just a slogan.

For the individual developer

  • Stop re-explaining your project to an AI

    The Brain is persistent and local. Context is assembled from the graph, not from your memory of which files matter.

  • Spend fewer tokens per task

    The agent asks the graph for signatures, edges and exact source ranges instead of reading whole files. Target: a context pack at most 25% of the naive baseline.

  • Know what a change breaks before you make it

    Impact analysis groups the blast radius into model, persistence, UI/state, background and tests.

  • Onboard onto an unfamiliar codebase faster

    Feature paths show screen → state holder → use case → repository → API or database, with evidence for every hop.

  • Stop tab-switching

    Run, device control, logs, tests, QA and reports live in the editor.

  • Test a real user flow without writing a test framework

    Describe a flow, review the plan, approve, run it on a device.

  • Reproduce a bug on demand

    Replay re-runs the exact flow from a declared initial state.

  • Trust AI changes

    Nothing multi-file is written without approval; every task can be reverted without losing unrelated edits.

  • Keep your code on your machine

    Local by default, no account, no network needed for Brain features.

For a small team or agency

  • QA coverage without a QA engineer

    Deterministic flows run on real hardware and produce shareable evidence reports.

  • Bug reports that are actually actionable

    Every failure carries a screenshot, the log window, the failing step, device details, the build and commit, and the source components likely involved.

  • Fewer "works on my machine" arguments

    The report records the commit, whether the tree was dirty, the variant, the device and the Android version.

  • Reusable flows across similar projects

    Flows are authored YAML committed with the project.

  • Safer AI adoption for client work

    Approval gates, audit trail, secret redaction and workspace boundaries are defaults, not settings to find.

  • Consistency across Android and Flutter

    One workflow, one report format, one set of interfaces.

For an engineering manager (Team edition, post-alpha)

  • See the architecture without opening an IDE

    An admin web console shows every project's graph, feature paths and activity.

  • Catch collisions before merge

    Two developers changing the same node — or within each other's impact radius — raises a warning on both sides.

  • Skip redundant indexing

    The server caches a base graph per commit; a developer opening that commit downloads it instead of indexing.

  • Measure AI spend honestly

    Token reports per project, team and developer, against a baseline.

  • Enforce architecture rules

    Layer rules (for example, UI must not call a DAO) are evaluated on the graph and runnable in CI.

  • Keep source off the server

    By default the server receives graph facts and team knowledge — names, kinds, edges, ranges, hashes — not source code.

Scope boundaries

What the first release will not do.

Published as plainly as the feature list, so the alpha can be judged against it.

  • No iOS execution, simulators or Xcode management. Flutter is supported on Android first.
  • No autonomous exploratory QA across every screen.
  • No visual-regression baselines across many devices; no cloud device farm.
  • No team collaboration server, hosted code, or hosted graph storage.
  • No backend or web project intelligence.
  • Not an Android Studio replacement: no Layout Inspector, no advanced profilers, no Compose Preview, no complete Gradle project modelling.
  • No automatic deployment, Play Store submission or signing-key management.
  • No POS-specific printer, card terminal, ECR or payment simulation — that is a later Globevik-specific edition.
  • No silent autonomous edits.