Load and inspect
Select a matching dynamic library and inspect its version, ABI and exported capabilities. The SDK is supplied separately and is not included in the source repository.
SOVKIT · DEVELOPERS
Bring nearby communication to your application.
Inspect the SDK with open-source DevTools, then integrate through its public interface. Start with a defined platform and a real communication task.
The integration contract
libsovkitsovkit.hIntegration guideDynamic library · Public C/C++ entry points · Platform-specific package
Start with DevTools
An open-source desktop workbench for SDK integration and troubleshooting. It does not require Nearvia or private SDK source to build.
Reproduce and diagnose
Use isolated test identities to inspect discovery, pairing, messaging and transfer behavior. Keep test data separate from your everyday Nearvia records.
Source first
The initial source release uses MIT. There are no packaged DevTools Releases yet. Windows and Linux details will be improved on those systems; cross-platform source is not proof of runtime validation.
Bluetooth scope
The desktop Bluetooth page exercises SDK frame interfaces. It does not provide system GATT scanning or advertising and is not a substitute for wireless Bluetooth acceptance testing.
Get a matching SDK package
The full SDK is not yet publicly released. Confirm availability for your platform before trying to build the workbench; DevTools source alone is not a runnable application.
Describe the target
Tell us the operating system, CPU architecture and whether you need local-network files or Bluetooth short messages. Do not post credentials or private business files.
Confirm the package and terms
Check the supplied platform library, sovkit.h, integration guide, version/ABI and license together. The DevTools MIT license does not license the SDK.
Build, connect, report
Follow the repository build guide, load the SDK, and reproduce one task with isolated identities. Include versions and minimal steps when reporting a problem.
Integration, platform adaptation and troubleshooting support can be discussed with a defined scope. Availability, deliverables and cost are agreed separately; no support plan is being sold here.
Open-source components
Components have their own licenses and release boundaries. A component release does not imply that the full SDK has been published.
sovkit-stun
IPv4 UDP STUN Binding server and C++ static library · MIT · Development preview. No TURN or payload relay.