Will you still be here, and can we get our data out?
Every board that has looked seriously at Veldun has asked some version of those two questions, usually in the same meeting. They are fair questions to ask of a young company, and they deserve answers you can check rather than reassurance you have to take on faith. Here are ours, in the order we think they matter.
First
The data is yours, by design.
Any administrator can export your organization's complete records on demand - members, households, dues history, events and registrations, documents - as a single archive, at any time, at no charge. No support ticket, no notice period, no request form.
More importantly, you do not have to remember to do it. Connect your organization's own Google Drive once, and every night Veldun writes that same complete export into a folder you control, under your own login. We keep the last seven nightly copies plus a monthly snapshot for each of the last three months, so there is always a recent archive and a few months of history sitting outside our systems.
This is the part worth being precise about, because it is architectural rather than a promise. Once the connection is in place, if Veldun disappeared tomorrow there is nothing to release, no escrow to trigger, and no credentials for anyone to hand over. Last night's copy of your data is already in your Drive, under your login. Getting to it never routes through us.
Two caveats worth stating plainly. The nightly copy only starts once an administrator connects a Drive - it is not on by default, and the dashboard will tell you if a night is missed. And each copy is a complete archive including your uploaded documents, so a media-heavy organization should point this at an account with room to hold about ten of them. Veldun requests the narrowest Google permission that exists for this: access limited to the folder it creates, and nothing else in your Drive.
Second
Support is a commitment, not a hope.
Running the platform is our job, not your board's. Site changes, newsletter drafts, event pages, migration and the support inbox are ours. What we need from you is the substance - what the event is, what the board wants to say - and your approval before anything goes live.
What we will not do is tell you a support story that sounds better than it is. Veldun is a small team, and the honest answer to “how fast will you respond?” is a published commitment you can hold us to rather than a name to ask for. Every inquiry gets a response within 24 hours. Incidents are classified by severity with response windows of 4, 8 and 24 hours. Uptime is committed at 99.9% monthly, and if we miss it you are owed service credits - not an apology.
High-severity incidents get a written report within five business days of resolution. All of it is in the service level agreement, which is a contractual document, not a marketing page.
Third
A platform that already outlived the business that built it.
Veldun is built by the team behind IndiBlogger, which grew into India's largest blogging community with more than 40,000 members. Running it meant a decade of the same problems Veldun exists to solve: memberships, events with unpredictable turnout, newsletters, and a public site that had to stay current.
That business wound down commercially in 2019. The platform is still running today, and support is still answered. We mention it because it is the most honest evidence we have for the question you are actually asking - not how big we are, but what happens to your organization when the commercial story changes.
Veldun itself is new, and we would rather say so than imply otherwise. The product is younger than the platforms it replaces and the feature set is narrower. What is not new is the habit of keeping something running after the excitement has passed.
Still want to poke at it?
Send the questions your board is actually asking, including the awkward ones. We would rather answer them now than have them surface after a contract.