3.6K
Open-source infrastructure control plane by Neko Nik, in partnership with YSPL.
One platform. Complete infrastructure control.
N-Ops is an evolving project. This README describes the product direction and intended capabilities; it does not claim that every feature below is already implemented or production-ready. Check the current source, release notes, and API documentation for implementation status and supported configuration.
N-Ops is an open-source platform for centralized infrastructure management, Linux server administration, secrets and configuration management, Docker orchestration, monitoring, auditability, and automation.
It is designed for developers, system administrators, and infrastructure teams who want to manage servers, environments, secrets, containers, files, logs, and remote operations through one control plane.
The project is intended to support self-hosted deployments and a managed SaaS offering with enterprise support and SLAs. It is designed for small environments through larger server fleets, with extensibility for integrations and custom monitoring extensions.
The following describes the product scope, not a guarantee that each feature is available in the current build.
Resources are organized as:
Organization → Project → Environment → Service → Variables / Files
.env import/export.Cryptography note: Argon2id is intended for deriving or protecting key-encryption keys from user-provided material; it is not an encryption algorithm. A production design should use authenticated encryption, envelope encryption, and documented key rotation. Secrets must never be written to logs in plaintext.
test, staging, and production.docker ps -a).Remote execution is security-sensitive. Production deployments should use least-privilege identities, scoped authorization, secure transport, and explicit policy controls.
Planned built-in host metrics:
Custom metrics and extension-provided checks are also part of the product direction. For example, a Postfix extension could report mail queue depth and trigger an alert when the queue exceeds a configured threshold.
Additional planned capabilities:
The current design direction is to store time-series metrics in Parquet files, including built-in and custom metrics.
The Parquet schema, partitioning, compression, retention policy, and query/index layer remain implementation decisions. The design should account for schema evolution, timestamps, server and metric identity, concurrent writers, and efficient time-range queries.
Planned remote file operations include browsing directories and files, creating/editing/deleting files, path-level authorization, audit records, and safeguards for sensitive paths and destructive actions.
A simple secure-notes capability is planned for operational notes and related sensitive information, protected by appropriate access controls.
PostgreSQL connectivity and query execution are under consideration, not a confirmed feature contract. If implemented, it should use explicitly configured connections, least-privilege database accounts, query auditing, and safeguards for destructive statements.
N-Ops is intended to provide durable job queues for remote operations and rollouts:
The planned command-center navigation includes:
N-Ops is designed around a central control plane and server-side agents:
This is a conceptual overview, not a guarantee of the current implementation or wire protocol. Refer to the source and API documentation for actual service boundaries and contracts.
N-Ops is intended to support self-hosted and managed deployments. Use the current release's deployment files and documentation for actual commands, dependencies, ports, volumes, environment variables, and supported database versions.
The project targets Docker Hub distribution. The exact Docker Hub namespace, image name, published tags, ports, and required environment variables must be confirmed from the official image listing and release documentation. Do not assume an image is published simply because Docker deployment is planned.
The official image name and tag are published at https://hub.docker.com/r/neko7nik/n-ops-main-api The pull command will follow this pattern:
docker pull neko7nik/n-ops-main-api:<TAG>
For production deployments:
latest.Source installation instructions will be documented once the runtime, dependencies, configuration, and supported startup process are established. Do not rely on guessed commands or environment-variable names.
The proposed managed SaaS pricing is usage-based:
Plan Proposed included usage
Free One user, up to 5 secret-store projects, and up to 10 servers Paid Custom pricing; first 5 projects and 10 servers included
Organization-level limits may also be configurable for users, projects, services, environment variables/files, and server inventory. These are proposed prices, not a statement that billing is currently available. Final pricing, billing intervals, taxes, and plan limits will be published with the managed service.
Infrastructure control planes handle highly sensitive credentials and privileged operations. Security is a core design requirement.
The intended security model includes organization- and resource-scoped RBAC, MFA, encrypted secret storage and controlled key management, least-privilege agent/API credentials, scoped read-only tokens, secret redaction, audit trails, and explicit confirmation/approval for dangerous operations.
Until a security review and production-readiness statement are published, evaluate the current implementation carefully before using it to manage production credentials or infrastructure.
Never submit real production secrets, private keys, or credentials in GitHub issues or public discussions.
N-Ops is intended to be fully open source, self-hostable, and community-driven, with development by Neko Nik in partnership with YSPL.
Contributions, bug reports, feature proposals, documentation improvements, and integrations are welcome. Before opening an issue, check existing issues and include a clear description, reproduction steps, relevant logs with secrets removed, and the version or commit you are using.
These areas represent product direction, not release commitments:
Track implementation status through repository issues, milestones, and release notes.
This project is released under the MIT license. See LICENSE. You are free to use, modify, and distribute this template for any purpose.
Content type
Image
Digest
sha256:fa3d08e6c…
Size
55 MB
Last updated
about 1 hour ago
docker pull neko7nik/n-ops-main-api