Company
Founder-led.
Evidence-first.
Ryntra is building a venue-neutral Risk, Strategy & Evidence OS for programmable assets: one Evidence Kernel, a human-facing Workspace, and a developer surface called Guard over the same core.
- Pre-launch
- Free beta
- No billing
- No token
One person is accountable for every claim on this site.
Ryntra began with a practical question: how can a person understand what they are authorizing before value moves — and prove what happened afterward? The product is being built in public through verified capabilities, explicit limits and human-controlled execution.
The work is founder-led and built with a rigorous AI-assisted engineering workflow: every change goes through code, tests and an explicit capability gate before it can be described as working. That workflow is why this site can bind its badges to a registry instead of to someone’s memory of what shipped.
There is no team page with invented names, no advisory board and no partner wall. When people join, they will appear here with what they actually do.
Product and engineering direction, capability truth, and the wallet that authorized the one recorded Arc Public Testnet transaction.
Where the company actually is.
Stated without rounding up, because a reviewer can check every line of it.
| Product stage | Pre-launch. A free beta with a Telegram confirmation controls capacity; there is no paid tier and billing is switched off. |
| What is usable | Wallet-signed Arcus spot RFQ on USDG↔TSLA, USDG↔AAPL and USDG↔AMD on Robinhood Chain, with separately scoped read-only account data, route readiness and RWA risk context. Every other execution pair is unsupported. |
| What is proven on Arc | One complete lifecycle on Arc Public Testnet — direct-eoa erc-20 usdc transfer of 1.000000 USDC, reconciled, with a receipt whose hash and integrity digest were recomputed independently of the application. View the transaction |
| What is not built | The general scanner, the personal workspace, the complete decision loop, multi-venue overlay, replay and robustness, professional order flow and guarded automation. All of it is in the register with its state. |
| Funding | Self-funded. No raise has closed, and none is announced. |
| Token | None. There is no token, no airdrop, no snapshot and no allocation — and no commitment to ever create one. |
Five commitments the product is built to keep.
Every material claim carries a source, an observation time and a scope. What is unknown is shown as unknown rather than smoothed into a number.
Software may prepare, evaluate and explain. It does not decide policy, supply a missing fact, or sign. That boundary is structural, not a setting.
For the same inputs, a free user and a paying user get the same evidence status, the same rule result and the same disclosed fees. Plans buy depth and scale, never a more permissive answer.
Nothing ships because a calendar said so. A capability moves when its evidence exists, and the register says where each one actually stands.
An artifact that does not exist is named as a gap. A disabled button pretending to be a feature is worse than an empty space with a reason in it.
What Ryntra is not.
Named here so nobody has to infer it from what the product happens not to do yet.
- Not an exchange, broker, dealer or liquidity venue
- Not a custodian: Ryntra holds no funds and has no withdrawal path
- Not a wallet replacement, and never a service that asks for a seed phrase
- Not a signal group, not a copy-trading service, not an autonomous trading bot
- Not a system that declares an asset safe, legal, compliant or profitable
- Not a substitute for legal, tax, compliance or investment professionals
- Not a token project: there is no token and no commitment to issue one
Published as bounded source: the Agent Control developer kit under Apache-2.0, and an older Arc extraction that predates the current source and proves no parity with it. Still not published: a demo video, a deck and a press kit. Each needs a secret scan or a separate authorization, and an empty link is worse than a stated gap.
The voice, and the animal it belongs to.
Ryn is Ryntra’s raven: the researcher and explainer, not a trader and never a signal. It appears where something is being taught — research notes, walkthroughs, the places where a concept needs a patient voice — and stays out of the parts of the product where money moves.
That separation is deliberate. A mascot standing next to an authorization screen is a nudge, and this product does not nudge.
What we are studying
Ryntra keeps its own written positions on the market structure it operates in. Nothing is published yet — these are the lines of enquiry, named so the direction is inspectable rather than implied.
- Market structure24/7 token behaviour against a 24/5 reference feed, and what that does to a stop.
- Tokenized assetsCorporate actions, ratios and issuer discretion as evidence rather than footnotes.
- Programmable moneyThe Arc dual-interface USDC problem: one movement, two Transfer events, twelve orders of magnitude apart.
- Decision evidenceWhat a receipt has to contain before a past decision can be reviewed at all.
- Instrument anatomyReading an instrument from its own documents, with unknowns preserved.
Research hub: in preparation. No article is published, so no article is linked. The topics above are working directions, not a content schedule.
Talk to us.
For product questions, integration conversations, ecosystem review or press: hello@ryntra.io. Security reports have their own instructions in the Handbook.
Ryntra is not an exchange, broker, custodian or adviser, and nothing on this site is investment, legal or tax advice.