Frequently Asked Questions

The Kete alpha is a closed, pre-release evaluation program. It provides early access to Kete so selected participants can test it in real development contexts, provide feedback, and help guide its direction before commercial release. Kete is experimental and not yet generally available.

The alpha is intended for engineers, architects, policy authors, and technical teams working with real, non-trivial codebases. Participants should be comfortable evaluating early-stage tooling and willing to share telemetry and feedback. It is not a public demo or freemium offering.

No. Alpha access is by invitation only, and we are not taking signups at this stage. We invite participants whose use cases align with Kete’s goals.

Yes. You may use Kete on real internal codebases and live development environments to evaluate how it performs in practice. This is encouraged — it’s the best way to generate meaningful feedback.

No. The alpha does not allow customer-facing use, production deployment, use in revenue-generating services, or reliance on Kete as an operational control. Kete should not be something your organisation depends on during the alpha.

Yes, internally, for evaluation — as long as Kete is not shipped to customers, your product or service does not rely on Kete to function, and you are not representing your product as “using” or “incorporating” Kete. Using Kete to explore, reason about, or test ideas is fine. Shipping it is not.

Yes, indirectly. You may learn from Kete’s outputs, reasoning, or diagnostics — but you should ensure Kete is not an ongoing required component, you can remove Kete without disrupting operations, and you independently validate outcomes.

Not without prior written permission. Because the alpha is pre-release and evolving, public benchmarks or comparisons can be misleading. If you’re interested in sharing findings, talk to us first.

No. The alpha strictly prohibits commercial exploitation, including resale, SaaS or managed offerings, and embedding Kete into products delivered to customers. Commercial licensing will be handled separately after the alpha.

Alpha access is time-limited (typically 3–6 months). At the end of the alpha, access to Kete ends and continued use requires a separate commercial agreement. There is no automatic right to keep using Kete. We’ll aim to have a clear path forward well before expiry.

Participation requires enabling telemetry, which may include feature usage, rule enforcement outcomes, errors and performance metrics, and correction feedback and weighting adjustments. Telemetry helps us improve Kete’s usefulness, accuracy, and validity.

We do not claim ownership of your code or data. Telemetry focuses on how Kete behaves, not on taking possession of your intellectual property. Where possible, telemetry is aggregated and anonymized. You remain responsible for ensuring your use complies with your own internal policies.

No. Telemetry is a condition of alpha access. If telemetry cannot run, the alpha is not a good fit.

Feedback (such as bug reports, suggestions, or design ideas) is assigned to us so we can incorporate it without legal ambiguity. You are not required to provide feedback — but it is strongly encouraged and highly valued.

During the alpha, we generally prefer feedback over code contributions. If code contributions are invited (for example, to open-source components like Ārai), they will be governed by separate contribution terms.

Yes. Some components associated with Kete (such as Ārai) are or will be released under open-source licenses (e.g., Apache-2.0 / MIT). However, the Kete alpha applies to the full Kete system, alpha access terms do not modify open-source licenses, and open-source components are governed by their own terms.

Kete is experimental. You should expect behavior changes, incomplete features, possible breaking updates, and occasional rough edges. This is normal for a alpha — and part of what we’re testing.

Support during the alpha is best-effort. We aim to respond to issues and questions, but there are no guarantees or SLAs.

The alpha agreement is governed by New Zealand law.

Yes. Access may be revoked if terms are breached, telemetry is disabled, or the alpha program changes or ends.