Evaluate usage against a useful task
Glyphs are units of CodeGryphon usage. Consumption depends on the working mode, available context and actions required, rather than file count alone.
Start with a clear, bounded result
Ask an architecture question, investigate a defect or run a focused audit. Define task boundaries so you can compare usage with the outcome.
A clear next step
Start in Desktop with a scoped task. Select a top-up in your account; current terms and the total appear before payment. Check your balance and confirmed credits in your account.
Adoption across a team
Agree on projects, access, use cases and acceptance criteria for a pilot. Deployment and support requirements are discussed separately.
Compare different kinds of work
A small fix, an architecture investigation and a release review require different amounts of work. Estimate your budget using representative tasks and compare glyph usage with results your team can accept.
Before adding glyphs
Check your balance, selected package and current total in your account. Glyphs are tracked on each participant’s personal balance. Discuss pilot scope and support terms separately for an organizational rollout.
Pricing
Loading packages…
Start with your team's project
Download Desktop, connect your project and start with a task whose result you can verify.