Mon, 21 Sept, 2:30 pm · Asia/Kolkata
Sunday Organic Market
Forty growers, every Sunday morning, free to enter.
The Ojas ecosystem
Who came, who paid, who contributed, what it cost, what was promised to whom. By Monday it is in four WhatsApp groups and someone's old phone. Ojas keeps it — tickets, contributions and the ledger on one record — so this year's utsavam (a temple festival), mela (a fair) or launch is where next year starts, instead of a blank sheet.
A committee secretary who took it on because nobody else would. A daughter organising her father's shashtiabdapoorthi (the rite for his sixtieth birthday). An operations manager with the annual dealer meet on top of her real job. A college fest convenor who graduates in April. Different occasions — exactly the same shape of problem.
A five-night utsavam, a Ganesh or Durga pandal (a festival marquee), Navratri, annadanam (a free community meal), a procession, a pilgrimage group. Donations in cash and by UPI, a hundred volunteers, and a committee that changes every year.
An RWA celebration, a society day, a ward function, a cultural association programme, a women's collective event, a health or cleanliness drive.
Mehendi, haldi and sangeet — the henna night, the turmeric ceremony and the music night — then the wedding, the reception, a housewarming, a naming. One occasion, five guest lists, and an uncle who promised the decorator something nobody wrote down.
A conference, an AGM, a town hall, a dealer meet, an award night, a college fest, a sports day, a convocation, an alumni meet.
An exhibition, a buyer-seller meet, a sourcing fair, a job fair, a product launch, a pop-up, a stall at a mela.
You are on the other side of it — the hall, the kitchen, the mandap (the wedding pavilion), the sound, the tent, the hotel, the college. You want the enquiry to arrive with the date, the headcount and the budget already on it.
Yours not listed? See every kind of occasion or who runs them.
None of these were written by a marketing team. They are the sentences people say once everyone has gone home.
An occasion is a burst. It builds for weeks, runs for a day or for five nights, and then everyone goes home. The people were real, the money was real, the promises were real — but none of it had anywhere to live. It lived in a group chat, a register, four phones and your head.
So when the occasion ends, the record ends with it. Not slowly — at once. The group goes quiet, the register goes into a cupboard, the phone gets sold, and the secretary hands over to someone new and hands over nothing, because there was nothing to hand.
That is why every year starts from zero, and will keep starting from zero. Not because nobody cared. Because the occasion was the only thing anyone kept, and an occasion is not a thing you can keep.
And whoever does keep the record takes the margin. The caterer remembers what you paid last year; you do not. The platform that sold your tickets keeps the list of who bought them. The hall knows its own occupancy; you know only that it was expensive. Every year you come to the table with no memory, and they come with five years of it.
A practice lives in a person. An institution lives in a system — a list, a written method, money that adds up, people you can hand over to, a name that travels without you. A temple that has run the utsavam for forty years still has no institution around it if the fortieth one starts on a blank sheet.
Not a nicer way to run the day. A record that is still there in November, and again the year after that.
Every night of a five-night utsavam is its own row with its own timing, venue and person in charge — while the tickets, the contributions and the counting stay on one event. You stop holding the shape of it in your head.
A drive with a public raised-against-goal page a contributor opens without an account, and — on your committee's own screen — a ledger with both sides on it: what came in, and what was spent on what. A confirmed contribution is recorded with its own reference. This is what a committee argument looks like when there isn't one.
Move the numbers. The refusals are the ones the checkout actually raises.
Only 4 place(s) left for this event.
With no capacity set, none of this runs. The guard is skipped entirely when the event’s capacity is blank, so the hall can be oversold and nothing objects.
The number on a ticket tier comes from somewhere else. Per-tier availability is the ticket product’s stock record, not this headcount, so a tier can read sold out while the hall still has room, or the reverse.
There is no percent-full anywhere. “Almost full” is 10 seats, not a proportion — because a tenth of a workshop is one seat and a tenth of a festival is two thousand.
Not a promise — the mechanism, so you can decide for yourself whether it would have helped last time.
The drag
LiveFinding a caterer or a decorator means asking a WhatsApp group, ringing four numbers off a list, and hoping whoever answers is any good — with nothing written down and no way to compare what each one quoted.
Ojas does this
Every vendor in the directory is reviewed by a person at Ojas before it appears, and you send a quote request from the vendor's own page — your date, your guest count, your budget — without creating an account. It lands in that vendor's inbox on Ojas with all of that already on it, so your request is on the record. Ojas does not sit in the middle of the conversation that follows — the vendor has your email and your brief, and any reply comes to you directly, outside Ojas. Nothing is sent on your behalf, nobody is chased for you, and no mail from us tells the vendor a request arrived.
You gain
Four vendors holding the same written brief, with your real date and headcount on it — instead of four phone calls where you explained it four different ways.
The drag
LiveA venue or a date can look available right up until two bookings try to claim it at the same moment — and you usually find out you lost it after you had already planned around it.
A temple utsavam, a Ganesh or Durga pandal, an annadanam, a society celebration — these are the occasions the code reaches furthest into, and it shows in what exists: a two-way contribution ledger with a public raised-against-goal page, a who-brings-what sign-up sheet, eco-kits scaled to your guest count, last year’s occasion duplicated rather than rebuilt, and each night of a multi-night utsavam invited and counted on its own. It is the same machine underneath a conference, a wedding or a trade show. It is simply deepest here.
See the festival productA contribution, end to end
Pledged on the public page
Recorded as pending, with the contributor's name and its own reference on it.
Confirmed by your treasurer
Once the money has actually arrived — by UPI, cash or bank transfer, outside Ojas.
Browse occasions by type and category, venues by place type, or vendors by service — every tile is a live count, not a guess.
Real occasions, venues, vendors and rentals, bookable today — not a mockup.
Mon, 21 Sept, 2:30 pm · Asia/Kolkata
Forty growers, every Sunday morning, free to enter.
The right-hand column is the longer of the two, and it is on the page rather than buried in an FAQ. You will find every line of it out for yourself in about a week, so there is nothing to gain by leaving it off.
The tenth utsavam knows what the first one cost. The committee changes and the handover is a login rather than a phone call to whoever kept the notebook. The tent-house quotes you and you are not guessing whether it is a fair number. A donor who gave last year is a name on a ledger you can open, not a memory somebody has to be trusted about. The people who came are a list your institution owns, and not the property of whoever sold the tickets.
That is the whole of it: the occasion stops being something you survive and becomes something your institution owns. Not because the day gets easier. Because the day stops taking its own record with it when it leaves.
None of that arrives whole, and here is exactly how far it has come. Today one occasion keeps its own record properly, and the next one starts from a copy of it. What does not exist is the view across years: no five-year comparison of one utsavam, no donor who is one person across five drives, no vendor score you can look up next time, and no export you can run yourself. Those are the direction, not the offer. If the reason you would buy this is the year-on-year picture, buy it next year, not this one.
Sell a maker's goods at your festival and each share is worked out and posted to a balanced ledger the moment the payment clears, rather than reconstructed afterwards — you read it on your own commission screen: the gross, the platform's cut, what that maker is owed, and whether you have recorded the payout. The maker has no screen of their own yet, so that figure still travels from you to them. Everyone you met adds to one list that keeps growing. And as you get bigger, the rest of what Ojas does — the legal side, credit and more — is already there. Splitting a co-hosted occasion's ticket takings between co-hosts is not among the things that work yet.
See the ecosystemThere is nothing to migrate. The occasion is living in a WhatsApp group, a Google Form and a register — nobody has to be told to stop using a system, because there isn't one. Which means trying this costs you one occasion, and the worst case is you go back to the group chat holding a record you didn't have before.
Create it, set your ticket types, open a contribution drive, invite people by function, and run the day on it. Start on the free tier and see it with your own occasion in it before anything else.
Start your occasionBrowse venues, and vendors a person at Ojas has reviewed, book a venue against live availability as a guest, and send a quote request with your date and headcount already on it — no account needed.
Browse venuesBefore you commit to a venue or a vendor, lay out what you expect to spend by category — venue, catering, décor, rentals — and track estimated against actual as the real numbers come in. It's a free planning tool tied to your account, not a booking.
Start a planAlready with us? Sign inNot hundreds of sign-ups. A handful of occasions, properly — because what we need right now is to sit through a real utsavam or a real dealer meet with the people running it.
Your real donation counting, your real vendor argument, your real door on the night — sat through with you and fixed properly, not answered with a help article. What you need that doesn’t exist yet gets built, because at this stage you decide what gets built next.
Including “this didn’t help”. We have built the machine and we have watched it run. What we don’t know is whether it works for your occasion — and you are the only person who can tell us.
Tell us what went wrong last time — the counting, the guest list, the vendor, the handover — and we'll tell you honestly whether this fixes it, including when it doesn't.
Tell us what went wrong last timeOr start your occasionA cost sheet with the expected figure and the real one side by side, line by line. Afterwards, a profit-and-loss for that one occasion — tickets, contributions, sponsorship, costs — which shows you nothing rather than a confident wrong number while any part of the picture is still missing.
An invitation where someone replies to the haldi and the reception rather than to the whole week, so the catering number is a count and not a guess. At the door, a QR that can't admit anyone twice — and that you can undo when it does go wrong.
Each vendor attached to the function they're serving, with the scope, the dates and the figure on the record. Send the family or the committee a read-only link and they see the same thing you do — no login, no account, no forwarded screenshots.
Duplicate the occasion and its name, dates, venue, description and ticket types come across into a fresh draft, and the checklist you wrote once gets applied again rather than retyped. It is not a full copy, and exactly what does and doesn't come with it is spelled out further down this page.
Ojas does this
Every booking checks and holds the actual slot the moment you commit, not afterwards — the same date, unit or stall cannot be sold to two different bookings.
You gain
If it shows as available, it is actually yours the moment you book. Not a maybe.
The drag
LiveA five-night utsavam or a three-day wedding is one occasion but five different guest lists — and on a spreadsheet the annadanam list, the procession list and the reception list all end up in one column, so nobody can tell who said yes to which night.
Ojas does this
Each function is its own row with its own timing, venue, budget, vendor roster and checklist, and a guest replying to your invitation picks which functions they are coming to — the haldi and the reception, not the whole week — while the tickets, the contributions and the counting stay on one event.
You gain
Replies that say which nights they are coming for, instead of one yes for a five-night occasion — and without running five separate events to get them.
On the ledger, both sides
What came in, and what was spent on what — itemised on your committee's own screen.
Fri, 25 Sept, 7:00 pm · Asia/Kolkata
A nine-night garba & dandiya celebration with a live dhol troupe.
Sat, 26 Sept, 2:30 pm · Asia/Kolkata
A free 90-minute session on export invoicing, LUT and refunds under GST.
Mon, 28 Sept, 2:30 pm · Asia/Kolkata
Two talks, pizza, and an hour of talking to strangers.
Mon, 5 Oct, 2:30 pm · Asia/Kolkata
A hands-on day with indigo, madder and myrobalan.
Fri, 9 Oct, 2:30 pm · Asia/Kolkata
The association's AGM — accounts, elections and the maintenance vote.
Stage, floral and lighting design for weddings, launches and festivals.
Full-service catering for weddings and corporate events — veg and non-veg menus, live counters, staffed service.
There is also no laboratory, no test report, no certificate of authenticity, no sensor reading and no animal or herd record anywhere in this software. Not thin — absent. If that is the reason you came, this is not that, and we would rather lose the conversation than have you find out in week two.
4 limits we published have stopped being true in the last year. See what changed, and when
A sound crew, a caterer, a decorator, a photographer. List what you offer and take enquiries that arrive with the date, guest count and budget on them. A person reviews the listing before it goes live — and the directory is early, so you would be building it with us.
List your businessAnyone with an occasion to run — a temple committee planning an utsavam, a pandal committee, a society running its annual day, a family planning a wedding, a company booking a conference, a founder launching a product, a college running a fest. You can browse venues and vendors here, book the venue and the rentals through Ojas, and run the occasion itself on Ojas. If you are on the other side of it — a hall, a caterer, a decorator, a crew — see 'List your business'.
That is exactly the case the record is for, and it is the one every tool gets wrong. If you ran a hundred occasions you would have built something by now. Running one a year is what makes it feel not worth writing down — and it is also why the fourth year still starts on a blank sheet. The value is not in this year's occasion being smoother. It is in next year's starting from this year's.
Be precise about this, because it is the whole point. Duplicating an occasion brings across its name, dates, venue, description and ticket types into a fresh draft. A checklist is separate: you write it once as a template and apply it again, and you author your own. What duplicating does NOT bring is the functions, the cost sheet, the vendor list, the contributions or the guests — those stay on the occasion they belong to, where you can still open them. So next year starts from something rather than nothing. It does not start finished.
Not by yourself, and here is the unflattering detail rather than the slogan. There is no export for attendees, contributions or the ledger — you ask us and we extract it for you. Contacts, leads, deals and an asset register do have real export jobs behind them. The occasion's own lists do not yet, and we would rather you knew that now than read 'export anytime' and found out on your way out.
No. Each occasion keeps its own record properly and you can open any of them, but there is no view that lines up five years of one utsavam, no donor who is one person across five drives, and no vendor score you can look up next year. That is the direction; it is not built, and this year is not the year to buy it for that.
The public drive page records the contribution as pending with the contributor's name against it, and shows the running raised-against-goal figure to anyone who opens it. Your treasurer confirms it once the money has actually arrived — by UPI, cash or bank transfer, outside Ojas — and confirming marks it against the drive. It does not email the contributor: that receipt is not wired. So it is a public pledge plus a permanent record, not an online payment gateway for donations.
No, and this is the one place we most refuse to be vague. The scorecard multiplies a fixed per-person figure for each travel mode — car, two-wheeler, public transport, carpool, walking — by what your guests ticked on their RSVP, and adds a flat allowance per head if you pledged to go plastic-free. There is no meter, no sensor, no sample and no certifying body anywhere in it. It is genuinely useful for comparing two ways of running the same occasion, and genuinely not a number to put in a CSR report.
Yes — create a free event plan, add expected costs by category (venue, catering, décor, rentals) and track estimated against actual as real numbers come in. It is a personal planning tool, not a booking, and it does not recommend vendors for you.
No, and we won't pretend otherwise. Ojas reviews every vendor before it appears in the directory and refuses listings that don't pass — but the contract for a caterer or a decorator is between you and them, and Ojas is not a party to it. What Ojas holds is the record: your quote request with your date, headcount and budget on it, and anything you paid through Ojas. Ojas does not carry the reply: your email address is on the request, so a vendor who answers answers you directly, outside Ojas — and because no mail from us tells them it arrived, a vendor who never opens that inbox never answers at all. A venue booking or a rental you pay for through Ojas is different — that money moves on our rail, and refunds go back the way you paid.
No — most bookings support checkout as a guest, with just your name, email and phone, and a quote request to a vendor needs no account at all. Creating an account lets you manage bookings, save a wishlist and check out faster next time.
Payments run through Razorpay or Cashfree — UPI, cards and netbanking. Those two are the only live gateways; there is no third. Ojas never stores your card details, and every payment webhook is signature-verified before an order is marked paid.
Cancellation and refund terms are shown on the booking before you pay. Orders you've placed can be cancelled from your account, and eligible refunds are processed back the way you paid.
Yes — create the event, set your ticket types and pricing, and sell through the same payment rail everyone books through, with your own organizer page. A ticket, a venue booking and a product can sit in one basket and land in one order.
There is no attendee import screen, so we do it by hand with you — your past attendees, your ticket types and your numbers. Run one occasion on it first if you'd rather not move everything at once. Nothing about the way you sell today has to stop while you try it.
We're not going to invent a customer list. Ojas Events is early, and you'd be among the first — that's the honest answer. What we can show you is the machine: the contribution ledger, the eco-kit scaler, the RSVP and QR doors, the cost sheets, the client portal and the duplicate-last-year path are all built and running, and you can see every one of them before you commit a rupee. If you run occasions regularly, we'll set the first one up with you.
Yes. Ojas builds the infrastructure that India's knowledge, land and rural enterprise become working businesses on — and builds it to sit lightly on the ground it comes from. Ojas Events is one of those lines: the occasions half of it, built deepest for temple utsavams, festivals and community gatherings. They all sit on the same foundations, which is why signing in once works across them.