About Ringske
Why I built Ringske
I am Elian. I build software, on my own, from Ghent. Ringske exists because Moya and I are getting married on Friday 21 May 2027, and because I could not find a planner that knows Belgium.
Elian, founder of Ringske
A shared document was not enough
We started the way a lot of couples do. A document, one row per invitation, a column for the headcount. That works until the questions start. Who has already replied? How many people are eating? Is aunt coming to the reception and not to the dinner? And when do we actually have to go to the town hall?
I asked those questions in the evening, not in front of a spreadsheet. Moya and I plan together. I wanted the answer in the same place, for both of us, without either of us hunting for the latest version in an email. So I started building Ringske. First for our own wedding. Other couples can use it now too.
Belgium was not in any checklist
The planners I found come from the United States. They do not know a marriage declaration. Here that is a window, not a date: at the earliest six months and at the latest fourteen days before the wedding, and many towns ask for it sooner. Ghent, where we file, asks for at least six weeks. Reserving the day is something else again. That is written out on the marriage declaration and in the timeline.
Our civil wedding is at Sint-Pietersabdij in Ghent. The party is a different moment. Guests therefore reply per part of the day, not with a single yes or no. Those two things, the legal window and a day in pieces, were in no template. They are in the wedding checklist.
On my own, from Ghent
There is no team behind Ringske and no agency building it for me. I write it myself. Moya plans the wedding with me. The code is mine. The company is ElianCodes BV, in Ghent. The details are on the contact page.
You can tell from the pace. I build what we ourselves need in order to be ready on 21 May 2027, and what other couples in Belgium need that same month: a guest list, a budget that does not pretend there is an average wedding, and a task list that moves when the date moves. what a wedding costs explains why I do not invent amounts.
What I do not put on this site
No reviews from couples I do not know. No stars, no "already a thousand couples", no badge that nobody awarded. If a real reaction ever arrives, I ask first whether it may go on the site, and only then.
Planning is free. Putting the wedding site online is a one-off payment. The amounts are on the pricing page. Guests need no account and no app. They open the link on the card.
What it is like to simply say the planning, in Claude or ChatGPT, is in a separate story about planning in Claude. This piece is the beginning: why I built it.
Read on