What it does
The kynetra binary sets up a standalone instance, starts it, installs it as a service on Linux, reads and writes data, replays the log, scaffolds starter projects and administers remote servers. Some subcommands act on a local data directory and others call the HTTP API. Setup, scaffolding, replay and the connection check have tests. Several front-ends are thin wrappers whose logic is tested in their own crates.
How it works
By default the tool opens a local data directory (--data, ./.kynetra by default). With --remote (or KYNETRA_REMOTE) and a bearer token, from --token, KYNETRA_TOKEN or a saved login, the data subcommands call the HTTP API of a server instead.
kynetra init writes a private, file-backed configuration with a generated API key kept in a separate key file. kynetra start launches the server from that configuration, and --dry-run prints the launch plan without revealing the key. kynetra status probes the configured server. kynetra install stages the binaries, the configuration and a hardened systemd service layout under --root, and --no-start leaves it disabled.
put, get, delete, filter, search and stats read and write entities. filter takes terms such as kind:user, country="DE", age>21, a path with ? to test for existence, and path~text for a substring, and ANDs them. search takes a query vector. replay reads the log by sequence range to the terminal, a filter or a fresh engine. rotate auth-secret --start and --promote run the two-phase signing-secret rotation. new scaffolds a project from a starter template, and new --list shows the templates.
Remote administration includes login and whoami, connect and doctor (see the connection bundle entry), infra (read-only views of the infrastructure ledger), provider import-env for DigitalOcean, admin for users, passwords and two-factor setup across one or all instances listed in a local file, and ingest, backup, migrate and policy, which are described under their own capabilities.
Where you reach it
- CLI
kynetra init [--bind ADDR] [--profile NAME] [--force]; kynetra start [--dry-run]; kynetra status; kynetra install [--root DIR] [--no-start] - CLI
kynetra put <kind> <json> | get <id> | delete <id> | filter <terms> | search <vector> | stats - CLI
kynetra replay --from-seq N [--to-seq M] [--into stdout|engine|filter] - CLI
kynetra new <template> [dir] | new --list; kynetra rotate auth-secret --start|--promote - CLI
kynetra login | whoami | connect | doctor | infra | provider | admin | ingest | backup | migrate | policy (with --remote)
Example
kynetra init --bind 127.0.0.1:8080
kynetra start --dry-run
kynetra statusLimits
- The local data subcommands open the data directory themselves. To work with a running server, use --remote.
- login --password and admin set-password take the password as a command-line argument, which shell history and process listings can record. Use a throwaway shell or clear the history.
- provider import-env supports DigitalOcean alone.
- The admin, backup, migrate and policy front-ends have no tests in the CLI crate itself. Their logic is tested in their own crates.
- kynetra install writes a systemd layout for Linux. It does not run on other systems and is not a cloud installer.
Evidence
- On this siteDocumentation hub
- TestsCovered in the engine repository by 5 lifecycle tests (init creates a private file-backed instance, init refuses to overwrite, start dry run hides the key, status probes the server, install stages a hardened layout), 4 scaffolding tests, 3 replay tests, 2 scheduling exit-code tests, 3 doctor tests and 11 ingest tests
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to try this against your own workload.