A world of data.
A clearer view.

Kresmion brings the three forces that move markets, macro, equities, and crypto, onto one screen. The signals are normally scattered: macro regime and rates on one site, SEC filings and 13F flows on another, crypto exchange flows and on-chain whale moves on a third. Kresmion pulls them into a single live view, every event tied to the source behind it. It's the data layer for an individual investor or small fund, not an advisor.

Yes. The beginner's guide at https://kresmion.com/guide walks through every tool on the platform, one at a time, so a fresh account can go from the terminal and research notes to the signal feed and watchlist with confidence. It's open to everyone, no account needed.

Yes. Portfolio positions are AES-256-GCM encrypted in your browser before anything leaves the device. Kresmion's servers store the ciphertext, never the plaintext. We can't read your positions even if we wanted to, the encryption key is derived from your password (or PIN, if you've set one) and never transmitted. This is a structural property of the system, not a policy we promise.

Direct messages are not end-to-end encrypted. They're encrypted at rest, but Kresmion can read them, unlike your portfolio, which is encrypted in your browser and unreadable to us. Server-readable messaging is what lets a shared ticker or signal render as a live, sourced object in the conversation and lets the @kresmion assistant deliver your alerts. Treat messages like a normal chat: don't send secrets, keys, or passwords.

A compound signal fires when multiple independent data sources converge on the same asset within a short window, for example, a 13F filing showing institutional accumulation, an on-chain whale moving into the ticker, and an OSINT cluster mentioning the company, all inside 72 hours. Each individual signal might be noise; convergence across uncorrelated sources isn't. Kresmion shows the convergence directly with source attribution.

No. Kresmion surfaces events with context and historical analogs. We don't tell you what to do, that's your call. This is a deliberate product decision, not a regulatory hedge. The platform is designed around the assumption that you're the analyst; Kresmion is the data layer, not the advisor.

SEC filings ingest within minutes of being filed at EDGAR. 13F flows ingest on the quarterly filing date. On-chain whale moves are tracked in real time across ETH, BTC, and SOL. OSINT clusters refresh every few minutes. The macro regime score recomputes once daily after market close. Each entity page shows its own last-updated timestamp so you can verify currency before acting.

Yes. Kresmion has a versioned REST API at /api/v1 with a live OpenAPI spec, documented at /developers. It needs an API key, and any free account can generate one under Settings, API Keys. There is also an MCP (Model Context Protocol) server at https://kresmion.com/api/mcp so AI assistants like Claude can connect through Sign in with Kresmion. Pull data through the keys directly, the Python SDK (pip install kresmion), or the Kresmion Excel add-in. The free tier is 10,000 calls per month. Real-time webhooks deliver signed callbacks for market events.

Kresmion is moving from free beta to subscriptions, and the plans are public at /pricing: Basic at EUR 20 a month for the app, Developer at EUR 80 a month with the API and MCP server, and Business on request, all ex-VAT. Billing is not switched on yet, so today you still create a free account with no card, and much of the public data needs no account at all. Accounts opened during the beta keep half price for their first 12 months once billing opens, and you are told before anything changes. No surprise charges, no trial countdown clock.

When you click Delete Account you're signed out everywhere immediately and your account enters a 30-day grace period. You can cancel any time during those 30 days by signing back in and confirming the restore, which fully restores the account. If you don't cancel, everything tied to your account, encrypted portfolio ciphertext, watchlist, alert settings, and usage history, is permanently purged from our database at the end of the grace period. Off-site encrypted backups are kept indefinitely as a disaster-recovery archive, and deleted data is never restored to the live service. The only thing we keep is a single anonymous deletion record with no identifiers, used for capacity-planning totals.