Loading page
The Ojas ecosystem
The machine behind every occasion you run — an utsavam or a pandal, a wedding, a trade show, a discovery day, a launch. Everything marked Live is built and you can open it; everything on the roadmap is flagged as not shipped and never mixed into the live surface. Ojas Events is early and we would rather you check this list than take our word for it.
Stand up an event, sell seats, and run a calm door — without re-keying last year.
Create from a festival template or one-click deep-clone last edition — every ticket type copies onto a fresh, isolated SKU, so this year can't corrupt last year's records.
Paid seats mint scannable, unguessable QR passes; check-in/out is reversible, timestamped and fully audited, with event-scoped door-staff roles.
A shareable RSVP link dedupes replies by email, captures party size and travel mode, and feeds the sustainability scorecard — separate from paid ticketing.
Sold-out demand queues; offers extend in order and auto-expire in 48h to the next person. The allocate → consume → cancel stock lifecycle means a seat can't double-book.
A mehendi and a reception, a keynote day and a workshop track — each function is its own row with its own timing, venue, budget, vendor roster and checklist, and guests reply to your invite function by function, while the money and the reporting stay on one event.
Build the agenda: every session with its window, its track and its room, and speakers attached to it. A room holds one session at a time, so a clash is rejected naming exactly what it collides with — you find out at the desk, not at the door.
Booths by number and size, each available, reserved or confirmed, with the exhibitor profile holding it. The plan geometry is stored but not drawn — a rendered floor-plan map is still made outside Ojas.
Attendees and exhibitors register what they bring and want — capital, sector, geography — from one public link. A weighted compatibility score ranks every possible pair and a solver picks the set of meetings that maximises useful conversations across the whole floor, inside each side's meeting cap and the venue's capacity. It is scored and solved, not guessed, and it is not AI. Your team sets each meeting's time.
One catalogue, one basket, one checkout — event tickets, add-ons and storefront goods together.
One order can hold an event ticket, an add-on and any product from your storefront — signed in or as a guest. Stock is locked as it sells, so the last unit goes to whoever pays first and the next buyer is told at checkout.
Collections scale by head-count — base quantity × (guests ÷ base) plus a buffer — so a committee knows exactly what to order for the number of guests coming. It works the list out for you; you still add each item to the basket yourself.
A public, tenant-scoped storefront with category trees, eco-certification filters and an 'arrives before your event' lead-time filter.
Voucher codes and batches (single-use, multi-use, once-per-customer) with validity windows, an anti-enumeration validate route, and per-order redemption.
India-first payments and a fund everyone can see — the committee's oldest headache, solved.
UPI, cards and netbanking via Razorpay and Cashfree, confirmed only after a signature-verified webhook — retries never double-capture.
A two-way (inflow + outflow) contribution drive with a public raised-vs-goal thermometer; the treasurer confirms pending inflows, which records each one against the drive. Confirming does not email the contributor — the receipt template is not provisioned.
Full or partial refunds straight from the order via real gateway calls, with an audit trail and reconciliation counters that retries can't corrupt.
Taxes and any service fee you set are itemised on every order, so a buyer sees what they paid line by line. Your Starter, Growth or Scale plan decides what you can use, enforced in the product rather than on the pricing page. We don't take a per-ticket cut today — paid tickets count against your plan's allowance instead.
Turn the room into a pipeline — every attendee and enquiry becomes a relationship you follow up.
Any attendee or enquiry becomes a CRM lead with an owner and a scheduled follow-up, so a buyer-seller meet doesn't evaporate with the event.
Contacts, accounts, deals and pipelines with a kanban board — the relationships outlive the event instead of dying in a stack of cards.
Per-event custom questions stay attached to the right attendee at sign-up, captured once and reportable later.
Turn ad spend into worked pipeline — paid campaigns, every lead in one inbox, and the analytics to see what's working.
Connect an ad account and build, approve and schedule paid campaigns from one console — behind a draft → approve spend gate, so a manager signs off before budget goes live.
Lead-ad submissions from Meta, Google and LinkedIn arrive via signature-verified webhooks, deduped by email and phone, and auto-assigned to an owner with a scheduled first follow-up.
Web forms, WhatsApp messages, CSV imports and Zapier relays flow through one tokenized endpoint — with de-duplication, a DPDP/GDPR consent ledger, referrer attribution, and the source campaign and ad logged on every lead.
Google Analytics 4 and Meta Pixel tracking out of the box — page views and standard events (view, lead, purchase) — plus trending-product analytics across your storefront.
Realised daily spend, impressions and clicks land per ad entity and roll up to the brand, venture or channel that owns the account — then sit beside the orders actually attributed to that spend. When Meta reports 40 conversions and you booked 12, you can see it.
Run the committee, not just the event — roles, who-brings-what, checklists, where every guest sleeps, what the crew's day cost, and next-season nudges.
Time-bound, event- or org-scoped roles — secretary, treasurer, procurement, invites, logistics, co-host — each gated to exactly the privileges it needs.
Publish a sign-up sheet of items and roles; guests claim anonymously (email-deduped) with live claimed-vs-needed tracking and close-when-covered.
Kit you own is reserved against an event and tracked per unit. Owners can opt a surplus unit onto a tenant-wide internal hire board, so another team's idle equipment covers your shortfall before you pay to hire it in.
Assign an attendee a room, a bed or a flat and read, on one roster, who is housed and who still isn't. The beds are ordinary bookable resources, so the same hold that stops a double-booked hall stops two families being given the same room.
Roster your crew to shifts, then mark the day's register: who was rostered, who actually turned up, and what that day cost. Marking someone present records the punches that compute the day — there is deliberately no field that accepts a hand-typed day count, so a crew payout is a measurement rather than an assertion.
Reusable per-festival templates whose tasks anchor to lead time (due = event − lead days), with assignment, done-tracking and a digest nudge.
Schedule next-season nudges ('Ganesh Chaturthi is 3 weeks away') over email and in-app, deep-linked to re-run last year's event.
Make the lower-impact choice the easy one, estimate what it changed, and share the card — with the estimate labelled as one.
Set green pledges per event; a scorecard estimates the difference from the travel modes your guests declared at RSVP and the pledges you made — no extra data entry. The travel modes are real; the CO₂ per mode comes from a fixed table of averages, so the figure is a comparison, not a measurement.
A public Green Charter page and a 1200×630 shareable card carry your pledges, the estimated CO₂ and plastic figures and the score out of 100 — generated from the event's own data, with no extra entry. It is a scorecard card, not an audited impact report: the emission factors are estimates.
Catalogue items carry an eco-certification and a CO₂ figure the maker states, and an 'Ojas Verified' badge marks a partner someone at Ojas has reviewed. Both are attestations — one by the maker, one by us — not third-party certification, and we say so on the product page.
WhatsApp deep links (wa.me) plus auto-generated OpenGraph images for events and scorecards make inviting and sharing one tap.
Your brand, your data, your tenant — on a multi-tenant spine with a typed API behind everything.
Every row carries a tenant — sign up and get your own branded console and storefront; out-of-tenant reads return 404, never 403, so there's zero cross-tenant leakage.
Team access is role → permission groups → privileges evaluated at a data scope — never platform staff flags — with time-bound grants.
Attendee, check-in, contribution, RSVP and waitlist figures, each on its own screen for the event; the orders, customer, voucher, offer and abandoned-basket reports read on screen and download as CSV; and any governed metric you chart on a dashboard exports as XLSX or PDF. Those downloads are the totals — a row-by-row export of every order and attendee isn't built yet.
Start a venture from a published Blueprint in your console and the whole thing is built for you — catalogue, pipelines, channels and dashboards, all from the design, and each application is installed once, so a re-run doesn't duplicate it. Buying a Blueprint as a paid Venture in a Box happens on the Ojas marketplace at ojas.vc, not from this site.
Everything an operator does is a typed JSON API with webhooks for external integrations — the same contract the frontend itself consumes.
A few capabilities are real but partial. We say so plainly rather than imply they're finished.
The horizons we're building toward — kept in a separate lane so a demo never implies they ship today. That candour is the point.
Later · Buying a Venture Blueprint works today, on the Ojas marketplace at ojas.vc. The reverse loop doesn't: packaging your own working events operation into a design other operators can buy is not built.
Phase 3 · Split-payments via Razorpay Route, seller self-onboarding and featured vendor placement — beyond today's single-merchant consignment. Group-buying thresholds are a partial case: the discount engine and the buyer-facing progress read exist in the API, but there is no screen for setting a threshold, so nobody can switch one on.
Phase 2 · Programmatic messaging on a real provider with a DPDP/GDPR consent model — replacing today's wa.me deep links.
Later · The production spine exists (bills of materials, production orders and runs, costed output) but has no console yet, and onboarding, training, certifying and scheduling small eco makers on top of it is unbuilt — today's floor is curated consignment.
Later · Matchmaking and meeting allocation are live today (scored and solved, not guessed). Still unbuilt: an assistant that drafts the follow-up, qualifies the lead and works the console for you.
Create your account, start from a template, and put a real event live today — every Live feature above is yours from minute one.
Start freeHow we help you grow