CLI and SDK design
Command, configuration and API surfaces that match the user workflow, with stable errors, automation-friendly output and examples.
Capability · Developer tooling
Tools engineers can inspect, automate and maintain
Neul Labs designs CLIs, SDKs, test and build tools, compatibility layers and open-source components around a repeated developer job. The work includes the unglamorous parts that determine trust: errors, packaging, upgrades, provenance, documentation and maintenance ownership.
What a delivery can include
The interface, release and maintenance model are designed together rather than added after the implementation.
Compatibility layers
Targeted replacements or extensions that preserve the valuable part of an existing interface while documenting the unsupported edge.
Release engineering
Tests, packages, provenance, versioning, changelog, supported-platform matrix and protected release ownership.
Maintainer handover
Contribution path, governance boundary, issue triage, security reporting, support expectations and a realistic maintenance or deprecation plan.
Release readiness
A repository is not yet a maintained product
Public code becomes dependable through boring, repeatable controls and honest status language.
Rights and licence
Source ownership, dependency licences, generated assets and contributor rights are understood.
Supported surface
Platforms, versions, interfaces and deliberate exclusions are documented and tested.
Secure release
Build inputs, package contents, tokens, provenance and human approval are reviewed.
Install and remove
Published commands resolve to real artefacts; uninstall and rollback are tested.
User evidence
Examples reflect real tasks, while benchmarks and comparisons include their method and limits.
Maintenance owner
Issues, security reports, compatibility changes and eventual deprecation have an accountable path.
Public evidence across the toolchain
The catalogue provides source-level examples. Availability, packaging, licence and compatibility should be verified at the linked repository for the version being considered.
Rust
brat
run several coding agents in parallel, safely.
Rust
rjest
run your Jest suite far faster, unchanged.
Rust
rpytest
cut pytest startup and collection overhead.
Rust
gity
make a huge git monorepo feel instant.
Rust
grite
track issues in-repo with no server.
Rust
recurl
fix curl 403s without rewriting anything.
Rust
rninja
cut warm Ninja/CMake build times.
Rust
stout
install Homebrew packages, much faster.
How open-source work creates evidence
Inspectability
A reviewer can see interfaces, implementation, tests, issue history and release decisions instead of relying only on a capability claim.
Reproducibility
A versioned example and benchmark let another engineer challenge assumptions and rerun the relevant workload.
Maintenance signal
Accurate metadata, resolved security reports and compatible releases matter more than repository count or launch-day attention.
Questions people ask
What developer tools can Neul Labs build?
Typical work includes CLIs, SDKs, test and build tools, automation, compatibility layers, local developer infrastructure and open-source libraries. A project begins with a specific repeated developer task and a measurable improvement.
Can you open-source an internal tool?
Yes after removing secrets and company-specific assumptions, auditing rights and dependencies, selecting a licence, defining the support boundary and deciding who will maintain releases and security reports.
How do you make a drop-in replacement safe?
Define the supported compatibility surface, run upstream and project-specific tests, preserve exit codes and configuration where promised, document deviations, add a fallback or rollback path and version the contract.
Does publishing a repository guarantee adoption?
No. Useful adoption depends on a real problem, trust, documentation, packaging, compatibility, responsiveness and continued maintenance. Repository creation is not treated as a marketing backlink exercise.
Start with the developer task, not the repository
Share the current workflow, tools, users, distribution targets and the maintenance commitment that is realistic.
admin@neullabs.com