Loading page
Grouped by what you are doing; partly live and not-started items come last.
Stand up an event, sell seats and run a calm door.
One action copies an event's details and each ticket type onto a fresh product. It does not copy functions, the checklist, the cost sheet, vendors, contributions or guests.
A paid ticket mints an attendee with a QR pass whose code cannot be guessed. Check-in is a state with a timestamp, so a re-scan cannot admit anyone twice, and it can be reversed.
One capacity count covers every ticket type, seats in open baskets included, so two carts cannot both take the last seat.
A shareable link dedupes replies by email and captures party size and travel mode. It is separate from paid ticketing.
An operator offers a freed place to someone in it, and they get a claim link by email that stays open for 48 hours and then lapses.
A mehendi and a reception each get their own timing, venue, budget, vendors and checklist. Guests reply function by function; money and reporting stay on one event.
Every session has a window, track, room and speakers. A room holds one session at a time, so a clash is rejected naming what it collides with.
Booths by number and size, each available, reserved or confirmed, with the exhibitor profile holding it. The plan geometry is stored but not drawn, so a rendered floor plan is made outside Ojas.
Attendees and exhibitors register what they bring and want from one public link. A solver picks the meetings that maximise useful conversations within each side's meeting cap and the venue's capacity; your team sets each time.
One catalogue, one basket and one checkout for tickets and goods.
A basket holds an event ticket, an add-on and storefront products, for a guest or a signed-in buyer, with one payment. Stock is allocated when the order is placed, so the last unit goes to the first order and the next buyer is told at checkout.
Each venue and rental books from its own page against live availability, as a guest. A venue is priced by the hour, night, day or month, as its listing sets.
Collections scale by head-count (base quantity × guests ÷ base, rounded up), so a committee sees what to order. You add each item to the basket yourself.
A public storefront with category trees, an eco-certification filter and an 'arrives before your event' lead-time filter. The certification is what the seller states.
Voucher codes and batches (single-use, multi-use, once-per-customer) with validity windows and per-order redemption.
India-first payments and a fund everyone can see.
UPI, cards and netbanking via Razorpay and Cashfree, confirmed only after a signature-verified webhook. Retries never double-capture.
A two-way contribution drive with a public raised-against-goal thermometer. The treasurer confirms pending inflows, which records each one against the drive; confirming does not email the contributor.
Full or partial refunds straight from the order, through real gateway calls, with an audit trail.
Taxes and any service fee you set are itemised on every order. Your Starter, Growth or Scale plan decides what you can use, and paid tickets count against its allowance rather than a per-ticket cut.
Enquiries land as leads; contacts and deals live on pipelines.
An enquiry from an enquiry-led event's public page lands as a lead in your default lead pipeline, where you give it an owner and a follow-up date.
Contacts, accounts, deals and pipelines, with a kanban board.
Per-event questions stay attached to the right attendee at sign-up and are reportable later.
Paid campaigns, every ad lead in one inbox, and spend beside sales.
Connect an ad account with the credentials you already hold, then build a campaign with a goal, budget and dates. Approving it deploys it to the ad network, so a manager signs off before budget goes live.
Lead-ad submissions from Meta, Google and LinkedIn arrive through signature-verified webhooks, matched against the people you know, with their campaign, an owner and a first follow-up scheduled.
A web form or QR code, an ad-lead connection, a WhatsApp number or an automation relay each get a source, and every submission lands in one inbox, where a possible duplicate is flagged for a person to decide, never merged automatically.
Daily spend, impressions, clicks and the platform's conversion count roll up to the brand, venture or channel that owns the account — then sit beside the orders actually attributed to that spend. Figures arrive by an API push; Ojas does not pull them from Meta, Google or LinkedIn.
Roles, who-brings-what, checklists, guests, crew and next season.
Time-bound, event- or org-scoped roles — committee secretary, treasurer, cultural secretary, volunteer coordinator, procurement lead, door staff and co-host — each with only the privileges its job needs.
Publish a sign-up sheet of items and roles. Guests claim anonymously, deduped by email, with live claimed-against-needed tracking.
Kit you own is reserved against an event and tracked per unit. A surplus unit can go on a tenant-wide hire board, so idle equipment covers a shortfall before you hire.
Assign an attendee a room, bed or flat and read who is housed on one roster. Beds are ordinary bookable resources, so the hold that stops a double-booked hall stops a double-booked room.
Roster your crew to shifts, then mark the day's register: who was rostered, who turned up, what the day cost. Marking someone present records the punches that compute the day.
Checklist templates you write once and apply to each event, with tasks due a set number of days before it, assignment and done-tracking.
Schedule an email nudge for a date, tied to last season's event; a scheduled job sends it when it falls due.
The lower-impact choice made easy, with the estimate labelled as one.
Set green pledges per event; a scorecard estimates the difference from the travel modes guests declared at RSVP and your pledges. The CO₂ per mode comes from a fixed table of averages, so it is a comparison, not a measurement.
A public Green Charter page and a 1200×630 card carry your pledges, the estimated CO₂ and plastic figures and the score out of 100. It is a scorecard card, not an audited impact report.
Catalogue items carry an eco-certification and a CO₂ figure the seller types in, and a partner can carry an 'Ojas Verified' badge that the storefront's own operators switch on. All three are attestations, not third-party certification.
WhatsApp links plus auto-generated OpenGraph images for events and scorecards make sharing one tap.
Isolated data, role-based access and a typed API.
Every row carries a tenant, and an out-of-tenant read returns 404, never 403, so one tenant's data cannot be read from another's.
Roles map to permission groups and privileges, evaluated at a data scope, with time-bound grants. Platform staff flags never grant access.
Attendee, check-in, contribution, RSVP and waitlist figures each have a screen. The orders, customer, voucher, offer and abandoned-basket reports download as CSV, and dashboard metrics export as XLSX or PDF; a row-by-row export of every order and attendee is not available.
Start a venture from a published Blueprint in your console and the whole thing is built for you — catalogue, pipelines, channels and dashboards, each installed once. Buying a Blueprint as a paid Venture in a Box happens on the Ojas marketplace at ojas.vc, not here.
A typed JSON API and webhooks for your own tools, the same contract the console consumes.
Directions for the venture. Each card says what exists today.
Buying a Venture Blueprint works today, on the Ojas marketplace at ojas.vc. Packaging your own working events operation as a design others can buy is not started.
Today is single-merchant consignment; split payments via Razorpay Route, seller self-onboarding and featured vendor placement are the direction. Group-buying has a discount engine but no screen to set a threshold.
WhatsApp share links work today. Programmatic messaging on a real provider, with a DPDP/GDPR consent model, is the direction.
Today's floor is curated consignment. The production spine (bills of materials, production orders and runs, costed output) has no console, and onboarding and certifying makers on top of it is the direction.
A form scheduled for publication through Meta is recorded here with a placeholder identifier, and nothing is created on the platform. Inbound lead webhooks and attribution work today.
The Google and LinkedIn adapters that send hashed contact details are built, but no screen creates an audience, so a push is never started.
Matchmaking and meeting allocation are live. An assistant that drafts the follow-up, qualifies the lead and works the console is not started.
A free account holds your tickets, orders and event plans. Ask to see any of it running.
Start freeSee solutions