VS Code ExtensionContext
Enterprise Knowledge Graph
KAVIA maps relationships across your codebase, giving analysis, planning and implementation a shared understanding of the system.
KAVIA AI for prplOS
Understand your platform. Accelerate your next engineering change.
Move platform upgrades, SoC integrations, Wi-Fi fixes and product changes forward with KAVIA AI. Use codebase-wide understanding to investigate issues, plan the work, implement changes and validate the result.
Pilot KAVIA on your own prplOS repository or project. Bring one engineering problem and put the platform to work.
01
Understand
02
Investigate
03
Plan
04
Implement
05
Validate
Engineering work needs more than a code suggestion.
A change in prplOS can cross the platform, vendor modules and your own customizations. KAVIA connects that context to the work your team needs to deliver.
Traceability
Source-linked analysis
Trace dependencies and findings to the relevant code. Understand why a change is needed and which components it may affect.
Delivery
Implementation and validation
Turn the plan into code changes and tests, then assess the work through your build, review and validation process.
Walkthrough
See KAVIA investigate a prplOS defect.
Follow a CWMP DNS socket-handle issue from source-code investigation to a proposed resolver-cleanup fix and the tests needed to check it.
Explore the prplOS investigationCWMP DNS socket handle
→ resolver cleanup path
→ proposed fix
→ tests to check it
Where to start
Which prplOS problem is on your roadmap?
Start with the change or issue holding up your product. Apply KAVIA to the code, customizations and validation that matter to your team.
01
Platform upgrades and migration
Move to the next prplOS baseline with your product customizations accounted for. Identify what carries forward, what needs updating and what can be retired. Develop the required changes and connect them to build and regression checks.
02
SoC, BSP and vendor SDK integration
Work across the boundary between prplOS and your silicon platform. Trace dependencies across the BSP, vendor SDK, hardware interfaces and build configuration. Use that context to develop integration changes and work through build and device-test issues.
03
prplMesh and Wi-Fi defects
Investigate connectivity, roaming and mesh-behavior issues across prplMesh and the platform code. Connect logs to the relevant source paths, examine the cause, implement a targeted fix and add regression checks for the original failure.
04
TR-181 interfaces and data-model changes
Follow a TR-181 parameter from its exposed interface to the backend implementation. Update the data model, service logic and integration together, with tests that check the changed behavior.
05
Product customizations and cross-repository features
Take an operator-specific requirement across shared components, vendor modules and product branches. Identify affected dependencies, implement the feature and check for regressions across the components it touches.
The workflow
From investigation to a change your team can review.
Understand
Map the relevant repositories, branches and product customizations.
Investigate
Trace the requirement or fault to the source and dependencies involved.
Plan
Define the implementation and the tests needed to assess the change.
Implement
Develop the code changes, patches and tests.
Validate
Run checks in your build or test environment and review the results.
The pilot
Make progress on a real prplOS task.
Use the pilot to tackle an upgrade, integration, defect or feature already on your roadmap. Work toward a code change your team can review, supporting tests and a clear view of the result.
Choose your repository or project and one problem to solve. We’ll shape the pilot around that work so you can evaluate KAVIA against your current engineering process.
Pilot KAVIA on your prplOS projectControl
Keep your code and releases under your control.
KAVIA supports customer-controlled deployment and repository access. Review patches before they are applied, keep write permissions separate, and retain your existing merge and release approvals.
Before you begin
Questions.
No. Tell us what you want to build, fix or migrate. You don’t need to upload code or connect a repository to get started. If we proceed, we’ll agree on access permissions and deployment before the pilot begins.
One agreed engineering task on your prplOS repository or project. Scope, duration, support and commercial terms are confirmed before you begin.