Vibe coding is fast.
Let's make it secure.

When you build by prompting AI, your code quietly logs emails, API keys, and customer data in plaintext. TN seals those fields in memory before they hit disk, so a logging breach gives up ciphertext, not your users. You keep the keys.

Get started GitHub

Without TN · TypeScript

// what the AI writes by default
console.log(`new user: ${email}, key: ${apiKey}`);

// your logs now hold this, in plaintext:
{"msg": "new user: [email protected], key: sk_live_9a2f3b..."}

The email and API key sit in plaintext in every log line, readable wherever those logs end up.

With TN · Python

# one verb, same idea
tn.info("user.created", email=email, api_key=api_key)

# sealed in memory before it ever hits disk:
{"event_type": "user.created", "email": "btn_cipher_9fa1...", "api_key": "btn_cipher_b412..."}

The same fields, sealed with keys you hold. A breach gives up ciphertext, not your users.

The problem: anyone who sees your logs sees your users.

Logs get stored, copied into dashboards, and shared with whoever's debugging. Anything you logged in plaintext travels with them.

TN locks the sensitive fields the moment they're written. The log still works. The private parts stay yours.

A logging dashboard showing TN events where every sensitive field is sealed, unreadable text — What anyone holding your logs sees: the sensitive fields are locked.

The same dashboard unlocked for an authorized reader, showing the real values in place — What you see, because you hold the key: the same fields, unlocked.

Two lines to start.

No new logging stack. Initialize once, then log the way you already do.

1 · Install

pip install tn-proto

2 · Use it

import tn

# Reads local keys and governance briefs automatically
tn.init()

# Log safely: PII is sealed in memory before hitting disk
tn.info("auth.user.login", email=user.email, ip=user.ip)

# Read your own logs back (fields come back decrypted)
for entry in tn.read():
    print(entry.level, entry.event_type, entry.fields)

3 · Back up & recover (non-custodial)

# Your first `tn init` prints a claim link: your encrypted keys + config
# attach to your account. The vault stores ciphertext only, never your keys.
tn init

# Recover on any machine from your recovery phrase:
tn wallet restore

1 · Install

npm install @cyaxios/tn-proto

2 · Use it

import * as tn from "@cyaxios/tn-proto";

// Reads local keys and governance briefs automatically
await tn.init();

// Log safely: PII is sealed in memory before hitting disk
tn.info("auth.user.login", { email: user.email, ip: user.ip });

// Read your own logs back (fields come back decrypted)
for (const entry of tn.read()) console.log(entry.level, entry.event_type, entry.fields);

3 · Back up & recover (non-custodial)

// `tn-js init` prints a claim link: encrypted keys + config attach to
// your account. The vault stores ciphertext only, never your keys.
npx tn-js init

// Recover on a new machine from your recovery phrase:
npx tn-js wallet restore --vault https://vault.tn-proto.org --out ./.tn

1 · Install

npm install @cyaxios/tn-proto

2 · Use it

// ESM package — use a .mjs file or "type": "module" in package.json
import * as tn from "@cyaxios/tn-proto";

await tn.init();
tn.info("auth.user.login", { email: user.email, ip: user.ip });

// Read your own logs back (fields come back decrypted)
for (const entry of tn.read()) console.log(entry.level, entry.event_type, entry.fields);

3 · Back up & recover (non-custodial)

// `tn-js init` prints a claim link: encrypted keys + config attach to
// your account. The vault stores ciphertext only, never your keys.
npx tn-js init

// Recover on a new machine from your recovery phrase:
npx tn-js wallet restore --vault https://vault.tn-proto.org --out ./.tn

By referencing a small governance file in your repo, your AI assistant writes these structured calls instead of raw print statements on its own.

Logs are great. Until they get passed around.

Logs are how you figure out what your app actually did. The problem is they rarely stay put. They get shipped to Datadog, read by support, scraped by an AI agent, pasted into a ticket, and left in a bucket someone forgot about. Anything you wrote in plaintext is now everywhere your logs went.

# looks harmless in your editor...
logger.info(f"login ok: {user.email}, token={session}")

# ...now it lives in five places you don't control

TN seals the sensitive parts inside your process, before the log is ever written. Pass the logs around all you like. The parts that matter stay ciphertext to everyone you didn't hand a key.