Skip to Content
We are live but in Staging 🎉
Feature Status

K3 Feature Status

Last validated: 2026-05-11

Status labels in this document:

  • Implemented: endpoint/service exists and is wired in API runtime
  • Partial: available but has known functional limits
  • Limited CLI: server supports feature but CLI coverage is incomplete

Storage Domain

FeatureAPI statusCLI statusNotes
Bucket CRUDImplementedImplementedCore bucket lifecycle available
Bucket policy CRUDImplementedLimited CLINo first-class bucket policy commands in current CLI
Bucket CORS CRUDImplementedLimited CLINo first-class CORS commands in current CLI
Object list/info/delete/urlImplementedImplementedRoute shape is path-based object key
S3 proxy fallbackImplementedN/AUnmatched routes are proxied to S3 backend

Source Domain

FeatureAPI statusCLI statusNotes
Source CRUDImplementedPartialCLI currently exposes source create; broader operations are limited
Credential CRUDImplementedImplementedStore/list/get/delete available
OAuth URL + code exchangeImplementedImplementedProvider flows supported
Credential validate/refreshImplementedPartialAPI present; limited CLI ergonomics

Pipeline Domain

FeatureAPI statusCLI statusNotes
Pipeline CRUDImplementedImplementedBasic lifecycle available
Template catalogImplementedImplementedAdmin templates list/get
List pagination behaviorPartialPartialPagination wiring is not complete in some list paths

Ingest Domain

FeatureAPI statusCLI statusNotes
Rule CRUDImplementedImplementedCLI command group uses ingest alias model
Trigger discoveryImplementedImplementedSource-scoped trigger route
Trigger ingestionImplementedImplementedSource-scoped trigger route
Sync statusImplementedPartialAPI present; less surfaced in CLI defaults
Ingest job list/statusImplementedImplementedAsync job visibility available

Vector Domain

FeatureAPI statusCLI statusNotes
Vector engine configure/get/deleteImplementedImplementedBucket-level vector engine lifecycle
VBase instance listingImplementedLimited CLIAPI exists under admin route
Add vector pipelineImplementedPartialCLI centered on older collection command shape
Add vector collectionImplementedImplementedManual collection path available
Collection list/get/deleteImplementedImplementedBasic collection lifecycle
Search (canonical route)ImplementedPartialCLI search uses compatibility path; canonical route is available for direct API callers
Search (compat route)ImplementedImplementedPOST /:bucket/search/vector
External vectors insert/upsert/deleteImplementedLimited CLIAPI present; no rich CLI command set
Batched hybrid dense+sparse search pairsPartialN/AExplicit unimplemented path in service logic

Tables Domain

FeatureAPI statusCLI statusNotes
Table engine enable/get/disableImplementedImplementedBucket-level table engine lifecycle
Table CRUD + schema alter/describeImplementedImplementedCore table operations available
Query/execute SQLImplementedImplementedQuery and execute routes exist
DML (insert/merge/update/delete)ImplementedImplementedExposed in table routes
Maintenance (optimize/vacuum/restore/history/compact)ImplementedPartialAvailable in API; CLI subset varies
Table pipeline creationImplementedLimited CLIAPI route exists; no first-class CLI command
Materialize tableImplementedPartialAPI exists; CLI coverage may lag

Platform and Operations

FeatureAPI statusNotes
Health endpointsImplemented/health, /healthz
Readiness endpointsImplemented/ready, /readyz with dependency checks
Metrics endpointImplemented/metrics Prometheus format
gRPC reflectionImplementedEnabled in gRPC server setup
Worker ingest/discovery/delete loopsImplementedEvent-driven async workers registered
Worker schedulers and GCImplementedPolling scheduler and ingest GC run loops

Compatibility and Drift Summary

  1. API architecture is fully split into six services; older monolithic naming still appears in some compatibility clients.
  2. CLI command coverage is practical but not complete for all exposed server capabilities.
  3. Some advanced feature paths are present but partially implemented, especially for certain vector search variants and pagination wiring.

Documentation Confidence

  • High confidence: route existence, service registration, middleware behavior.
  • Medium confidence: behavioral edge cases that depend on external systems (Scriptum/Ignite/VBase runtime conditions).