Changelog
Public ship log
See what actually changes in Vantnod.
Vantnod's changelog is not a decorated roadmap or a list of stray updates. It is the public trace of what has actually changed in the product, why the change was made, and how it affects the user's day.
We record significant changes to the product surface, Noa, data, approval gates, audit trail, EU readiness, pricing, and the external product.
Upcoming items are kept separate from finished ones. Beta is kept separate from production. Design decisions are kept separate from features the user can already use.
Status
01 / 06
Shipped, beta, and roadmap don't mean the same thing.
The changelog's main job is to keep promises honest. That is why every entry is tagged with a status.
- The change is complete and available in the environment the entry refers to.
- The change is in limited use or testing. It may still shift based on user feedback.
- An important product or architecture decision is made, but it may not yet be available to the user.
- The item is planned or in the build queue. It is not yet complete.
- An older model, view, or decision is being removed or replaced.
Latest changes
02 / 06
The product surface only changes for a reason.
Each entry tells three things: what changed, why it matters, and what the next user-visible impact is.
- 2026-06ShippedSurfaceBrand
The public site moved onto Brand System v1.
Every public page was brought onto one design language: bold Gragien headlines, a single clear-blue accent, and a recurring flow signature.
- What changed
- Home, Product, Pricing, the audience pages, Security, EU-Ready, and Contact were rebuilt on a consistent bar with oversized display type, editorial section counters, and the flow motif. Two new pages were added: Markets and Careers. The body copy was cleaned of em dashes across all four languages.
- Why it matters
- A finance product should look as exact as it is. A consistent, restrained system reads as more trustworthy than a page-by-page patchwork.
- Impact on the user
- The site reads as one product in Finnish, Swedish, Estonian, and English. Careers points to hiring at Impact Node, and markets are labelled honestly: Finland live, Sweden and Estonia in progress.
- 2026-05ShippedSurfaceBrandTrust
The external surface was rebuilt.
Vantnod's external surface was updated to better match the product's character: calm, precise, European, and trust-building.
- What changed
- Product pages, pricing language, Volume I voice, contact intake, and builder visibility were unified. The About page was rebuilt as a Volume I narrative, the Contact page as an intake surface with a privacy warning, and the menubar adapts to dark and cream surfaces.
- Why it matters
- A finance cockpit has to feel trustworthy before login. If the external surface is confused, the user has no signal that the internal product is precise.
- Impact on the user
- Vantnod's value proposition, contact, pricing, and way of building are easier to understand before the first message or purchase.
- 2026-05ShippedProductComplianceAuditSecurity
Onboarding and a compliance gate were built in.
Joining Vantnod was reshaped into a seven-step flow where identity verification, company lookup, and plan selection happen inside the same surface.
- What changed
- Onboarding was rebuilt as stages: welcome, sign-in, personal details, company (with PRH/YTJ lookup), Stripe Identity check, plan, and confirmation. Card details are collected up front for paid-tier trials, and higher tiers offer a demo account instead.
- Why it matters
- A finance product cannot be sold without a traceable identity and company. At the same time, the user experience has to stay calm: one person, one chain of responsibility.
- Impact on the user
- During onboarding the user already sees which company Vantnod is connected to, who is in the register, and which tier fits the situation. The demo path reduces pressure toward immediate higher payments.
- 2026-05ShippedPricingEU
Pricing was rebuilt into Volume I tiers and expert add-ons.
Tiers were rebalanced and expert help was split out as separate packages. VAT is shown both inclusive and exclusive.
- What changed
- Paid tiers are now Tähti (€29/mo), Virta (€49/mo), and Runko (€89/mo), with a free Kipinä floor. Setup, Compliance, Expert, and Ops Pack are offered as separate expert add-ons. Prices display VAT-inclusive (FI 25.5%, SV 25%, EE 22%), and Stripe Tax handles VAT-OSS.
- Why it matters
- Software alone does not cover the actual work a small company's finance needs. Separating the software tier from expert help lets pricing support real growth, rather than forcing the user to prepay for features they do not yet need.
- Impact on the user
- The user can start on an affordable tier and add expert help when there is a real need. VAT-inclusive prices are visible up front; the final receipt does not surprise.
- 2026Design decisionProductTrustSurface
Volume I is separated from a finished launch.
Vantnod's first public phase is defined as Volume I. This makes the early product more honest: the user sees what is already built surface, what is limited use, and what is still on the roadmap.
- What changed
- The Volume I voice, buyer surface, and early-user expectations were aligned.
- Why it matters
- The user no longer has to guess whether they are joining a finished mass product or an early phase. This reduces ambiguity and makes buying more transparent.
- Impact on the user
- Vantnod can state directly what is available now, what comes next, and where user feedback has the most leverage.
- 2026Design decisionRuntimeNoaAudit
Noa's suggestions are bound to approval gates.
Noa is not allowed to operate as a black box. Its job is to help the user understand finances, not to make accountable decisions on the user's behalf without a visible basis.
- What changed
- Approval gates were defined in Noa's decision model: where Noa can suggest, where it needs user approval, and where the action must be left to a human.
- Why it matters
- Automation in financial data is useful only if the user can see what is happening and verify the basis.
- Impact on the user
- Noa's suggestions are built around sources, limits, and approvals. Vantnod is not chasing a "magic bot", it is building a verifiable finance assistant.
- 2026Design decisionDataEUCompliance
Jurisdictions and obligations are brought into the base model.
European financial administration is not one unified model. Country, company form, VAT, invoicing, payment methods, and reporting obligations all affect what the user has to see.
- What changed
- An EU-first base model was added to Vantnod's data thinking: country, company form, obligations, and finance stack shape how the user view is built.
- Why it matters
- The same view does not serve a Finnish limited company, an Estonian company, a Swedish operator, or a sole trader in the same way. A finance product has to understand context.
- Impact on the user
- Vantnod's questions and recommendations can be more precise going forward: which country the company operates in, which company form it is, and which decision is waiting for information.
Trust
03 / 06
A good product company shows what it does.
- [01]
No invented history
We do not fill the changelog with retrofitted updates. Entries refer to real shipments, decisions, or visible changes.
- [02]
The user understands the change
Every entry explains why the change matters day to day. "Improved experience" is not enough.
- [03]
The roadmap stays honest
Future items are marked as future. Beta is not shipped. A design decision is not the same as a finished feature.
- [04]
Financial data demands traceability
When money, reports, sources, approvals, or obligations are involved, the change must leave a clear trail.
What we track
04 / 06
The changelog covers more than the UI.
In a finance cockpit many important changes happen below the surface: in the data model, in approvals, in sources, in roles, or in what Noa is allowed to do.
Surface
We record when the buyer, user, or team surface changes.
Noa
We record Noa's limits, suggestions, sources, and approval gates when they change.
Audit
We track changes that affect verifiability, approvals, user roles, or decision history.
EU & data
We separate real EU, Peppol, ViDA, and jurisdiction-readiness changes from marketing talk.
Pricing
We record material changes to tiers, limits, usage, or packaging.
Security
Privacy, access, and financial-data handling are changelog-worthy even when they do not appear in the UI.
Roadmap visible
05 / 06
Future items are stated as future.
Vantnod's roadmap is not a promise of everything at once. It is a view of what is being built next and on what logic.
- Stripe live mode smoke tests and webhook verification
- Wiring Stripe Connect V2 webhook to live events
- Onboarding follow-up: harmonising error states
- Direct Vero API integration (authorisation paperwork ready)
- Stripe Issuing application and card limits
- EU jurisdiction model extended to Estonia and Sweden
- ViDA readiness (e-invoicing 2028)
- Peppol sender integration
- Accountant multi-tenant view
A roadmap entry does not mean the feature is finished. When it is finished, it moves to the changelog as a shipped entry.
Start
06 / 06
Want to know whether a feature is ready?
Ask directly. We separate finished, beta, and roadmap from each other. If you want to know whether Vantnod fits your current finance stack, share the country, company form, current tools, and the decision that too often waits for information.