Features

What Nokuo can store, with typical examples and why each category needs encryption.

Why all of this needs encryption

What you put in Nokuo isn't ordinary notes — it's sensitive data. A leaked API key drains your bill, a leaked database password dumps your data, a leaked SSH key compromises your server. These resources sit scattered in .env files, chat logs, and old projects as plaintext. Nokuo brings them into one local encrypted Vault, stored by type with structure, ready to use while coding.

For the full list, see the Features page.

API credentials

Third-party service credentials. A leak allows direct API calls on your behalf.

API Key / Secret: OpenAI, Stripe, GitHub PAT
Access Token / Refresh Token: OAuth2 tokens
OAuth Client ID / Secret: app registration credentials
Webhook URL + Secret: payment / notification callbacks
Service Account Key: GCP / Firebase

Passwords

Web account passwords: any site login
App / email accounts: desktop apps, email
Recovery / backup codes: fallback access

Databases

Database connection info. A leak allows direct read/write of your data.

Connection string / DSN: postgres://, mongodb+srv://
Connection parameters: host / port / db / sslmode
Pooling config: pgBouncer, Prisma datasource
Redis / MQ connection: redis://, AMQP

SSH / servers

Server login credentials. A leak allows direct login to your servers.

SSH private key: id_rsa / ed25519
Server login info: IP / port / user
Bastion config: bastion chain
Known host fingerprints: known_hosts

Cloud / infra

Cloud platform and infrastructure credentials. A leak gives control over your entire cloud footprint.

AWS Access Key / Secret: IAM credentials
GCP Service Account JSON: service account
Azure connection string: Storage / SQL
kubeconfig: K8s cluster access
Terraform / IaC state credentials: remote state
CDN / object storage credentials: R2 / OSS / S3 access key

CI / CD

Continuous integration and release credentials. A leak allows tampering with your release pipeline.

GitHub Actions secret: repo variables
GitLab CI variable: pipeline variables
Package publish token: npm / pypi / Maven
Docker registry credentials: ghcr / harbor

Code / docs

Code and knowledge reused during development. Some contain sensitive info that needs encryption.

Code snippets: common functions / templates
Runbook / common commands: ops scripts
SQL query templates: troubleshooting queries
Regex / config snippets: reusable snippets
Project docs / context notes: architecture notes
API docs / schema: OpenAPI / Protobuf

Environment config

Deployment and runtime configuration. Often contains passwords and tokens.

.env snippets: full env blocks
docker-compose secrets: passwords / tokens
nginx / reverse-proxy config: server blocks
App config: yml / toml / ini

Software / licenses

Software licenses and subscriptions. A leak allows theft and misuse.

Software license keys: JetBrains / Office
Subscription serials: activation codes

Personal / other

Personal sensitive information. A leak enables identity theft or payment fraud.

ID documents: ID / passport
Payment / banking: card number / IBAN

Not supported yet

TOTP seed generation and crypto wallet seed-phrase protection are planned for a later release.