Workflow
Work interactively or script it cleanly.
Use the REPL for day-to-day investigation, run one-shot commands for automation, or execute stored scripts for repeatable operational work.
Initial public release
Treat Oracle, MongoDB, DynamoDB, and more like one SQL estate.
FedCLI gives operators one SQL-first surface across relational, document, key-value, graph, search, and time-series systems. When a federated query spans unlike sources, FedCLI can stage source rows into an execution workspace and run the final join or aggregation there.
Need rollout status, a walkthrough, or another public registry? Request access.
- Use one SQL-oriented operating model across relational and non-relational engines
- Join Oracle, MongoDB, DynamoDB, and other sources in one federated workflow
- Push down when possible and stage mixed-source joins when direct remote execution stops
DBACLI-SQL
Make non-relational systems operationally legible to SQL users.
Collections, documents, labels, indices, and cloud NoSQL tables can be exposed through a SQL-like surface so teams do not need a separate day-to-day tool and mental model for every backend.
Execution
Join unlike systems without pretending the sources are identical.
Single-source federated queries can run directly on the remote target. Mixed-source queries can be staged into an execution workspace for final joins, filters, and aggregations.
Get FedCLI
Where to get FedCLI and how to start it today.
FedCLI is available through Homebrew, npm, Docker Hub, GitHub Container Registry, AWS ECR Public, Azure Container Registry, Google Artifact Registry,
and GitHub Actions. Docker is the fastest zero-host-install path; Homebrew gives macOS and Linux users a SHA-256-pinned host install. The npm package gives you a host-visible
fedcli command and bootstraps the verified runtime jar on first use.
The supported modes today are interactive REPL, one-shot command execution with -c, and
script execution with @file.sql.
Docker Hub
Use the published image
Docker Hub is the quickest public acquisition path. Use :latest for the fastest start,
or pin a release tag such as docker.io/ronwarshawsky/fedcli:1.0.4 when you need
version-locked execution.
docker run --rm -it docker.io/ronwarshawsky/fedcli:latest
This starts with empty local state. To persist aliases, history, drivers, credentials, licenses, or local metadata, mount a named volume that is unique to one human or isolated environment, for example -v fedcli-home-alice:/var/lib/fedcli. Never share that volume across identities.
Homebrew
Install on macOS or Linux
The official Homebrew formula installs the immutable FedCLI release and its Java 17 dependency on macOS or Linux.
brew install applextech/tap/fedcli
fedcli --help
The formula pins the release JAR by SHA-256. Run brew update and brew upgrade fedcli when you want a later release.
npm
Install the host command
The npm package @applextech/fedcli is now public. It installs the
fedcli launcher, then downloads and verifies the matching runtime jar on first use.
npm install -g @applextech/fedcli
fedcli -h
If you prefer a project-local install, run npm install @applextech/fedcli and then
use npx fedcli --fedcli-runtime-info or npm exec fedcli -- --fedcli-runtime-info.
The package also installs dbcli as a temporary compatibility alias during the rename transition.
Java 17 or newer is required. If your machine resolves an older Java, the launcher stops early and tells
you to install Java 17+ or set FEDCLI_JAVA, legacy DBCLI_JAVA, or
JAVA_HOME to a compatible runtime.
Runtime
Use
Use docker run for shell, help, jobs, and scripts
Use docker run, not docker exec. FedCLI uses a direct CLI entrypoint, not a
background service waiting for later exec calls.
docker run --rm docker.io/ronwarshawsky/fedcli:latest -h
docker run --rm docker.io/ronwarshawsky/fedcli:latest -c "HELP"
docker run --rm -v "$PWD/ops-check.sql:/work/ops-check.sql:ro" docker.io/ronwarshawsky/fedcli:latest @/work/ops-check.sqlChoose the registry that fits your cloud boundary, or use the Action in CI. The complete registry and GitHub Actions commands are maintained in the cross-platform installation guide.
Documentation
Start from a concrete operating workflow.
The FedCLI documentation keeps installation, federated-query, database-support, automation, and AI-assisted SQL guidance in separate, linkable pages. Each page states the current public release boundary rather than implying that planned service capabilities are already a finished product.
Install
Run FedCLI with Docker, Homebrew, or npm
Choose an interactive shell, one-shot command, or mounted script and keep local state isolated per operator.
Federate
Join unlike database systems
See the direct-versus-staged execution model for federated SQL workflows.
Automate
Turn proven commands into scripts
Use the same CLI surface for repeatable checks, exports, and scheduled operational work.
Command Gallery
Show the product through real commands and high-value workflows.
These examples come from the current FedCLI surface and are grouped around the workflows buyers and operators usually care about first.
Capabilities
Built for real operator loops across SQL and non-SQL systems.
Classic CLI ergonomics
SQL*Plus-style commands, psql-style shortcuts, tab completion, history, formatting, and pagination.
SQL over non-relational systems
Query MongoDB, DynamoDB, Neo4j, Elasticsearch, Bigtable, and other non-RDBMS platforms through a SQL-like operating surface.
Federated joins across unlike sources
Create saved aliases, reconnect by name, and join Oracle, PostgreSQL, MongoDB, DynamoDB, and other systems in one statement.
Adaptive execution placement
Execute directly on one remote alias when possible, or stage rows for local execution when a mixed-source join or aggregation needs a shared working set.
Export and import
Move data through CSV and JSON, export schema with optional data payloads, and preserve repeatability.
AI-assisted SQL
Generate SQL from natural language, ask for syntax help, and manage provider configuration directly from the CLI.
Plugin support for more JDBC databases
Install additional JDBC drivers at runtime with PLUGIN SEARCH and PLUGIN ADD when a target sits outside the built-in catalog.
Automation-friendly
Use `-c` for one-shot execution or `@script.sql` for scripted jobs, wrappers, and operational runbooks.
Portable container delivery
Run the same product as a local JAR or a Docker image for REPL sessions, one-shot commands, and scripted operational work.
Enterprise Architecture
Built for serious private federated deployment patterns.
FedCLI is designed for organizations that want a private federated data operating layer inside their own environment. It can execute directly on source systems when possible, stage cross-system work when the workflow spans unlike platforms, and it already includes listener and worker runtime foundations for larger private deployment patterns.
Deployment Control
Keep the execution boundary inside your environment.
Place FedCLI close to your own databases, networks, operational controls, and support processes instead of routing sensitive cross-system work through an external managed service.
Federated Foundation
Move beyond one-off cross-database demos.
Saved federated aliases, staged multi-source execution, and listener or worker runtime foundations are already part of the product direction for teams planning heavier internal federated operations.
Current Contract
Enterprise direction, honest release boundary.
The public supported release today remains centered on interactive CLI, one-shot commands, and scripted operational workflows. Larger service-style deployment patterns should be treated as planned private architecture direction, not as a finished public turnkey control plane.
How Teams Use It
One workflow surface from ad hoc query to repeatable operations.
Connect once
Define known databases and federated aliases so operators stop copy-pasting fragile connection strings.
Query and join across unlike systems
Run SQL-style commands against relational and non-relational sources, then federate them together when the workflow crosses system boundaries.
Automate or package safely
Move proven commands into scripts, jobs, or containerized execution flows while keeping one operator-facing surface and one release contract.
Supported Engines
Broad coverage across operational, analytical, search, graph, and time-series systems.
The list below reflects the current built-in engine catalog. If your estate includes another JDBC database, FedCLI can extend coverage at runtime through its plugin system without rebuilding the core product.
Plugin Databases
Extend beyond the built-in catalog when the target is JDBC-based.
Search Maven Central, install the driver at runtime, and then connect normally. Plugin databases extend JDBC coverage; they do not replace built-in native support for MongoDB, DynamoDB, Elasticsearch, Neo4j, Bigtable, and similar engines.
Plugin
Add a JDBC driver at runtime
Use the plugin system for additional JDBC databases that are not already covered by the built-in engine catalog.
PLUGIN SEARCH hsqldb;
PLUGIN ADD hsqldb;
CONNECT 'jdbc:hsqldb:mem:demo';Honest Launch Boundary
What the current public release is, and what it is not.
Current release supports
- Interactive CLI usage
- One-shot command execution
- Repeatable script execution
- Cross-source federated queries across SQL and SQL-shaped NoSQL sources
- Container delivery for REPL, one-shot `-c`, and `@script.sql` execution
- Runtime plugin installation for additional JDBC databases
- AI features with user-supplied provider configuration
Current release does not claim
- A finished always-on listener/worker control plane
- A daemonized container model based on `docker exec`
- That every plugin database has the same native depth as a built-in engine
- A hidden managed AI service layer
- A database GUI replacement strategy
- Magic abstraction over actual SQL and operator judgment
Contact
Request a preview, discuss deployment, or ask for a walkthrough.
Why reach out now
- You manage multiple database engines and want one serious SQL-oriented CLI surface.
- You need Oracle, MongoDB, DynamoDB, search, graph, and similar systems to feel operationally consistent.
- You need containerized CLI delivery with supportable production artifacts.
- You want AI assistance without handing query control to a black box.
Current contact path: memfix@applextech.com