Skip to content

Features by business

StayCraft for NGOs & communities

Features and prices as of 7 November 2026.

For NGOs and trusts, self help groups, clubs, residents' welfare associations, and temples and religious trusts. Everything below is built (stage 1), unless it says (coming). Ready for sale: its page and footer link show once the kind is switched on sale on the operator's Kinds page.

What every site gets

These are on every community plan.

  • Your own website at yourname.staycraft.co.in, on the Lantern design: your mission, your numbers, your programmes, your committee, your updates and a Donate button on every screen.
  • Your documents, open to all: registration and 80G certificates, annual reports and audited accounts as PDFs anyone can download, each shown or kept back by you.
  • A volunteer form: people who want to help arrive under Messages, marked as volunteers (on Growth and above, as volunteers with their skills and hours).
  • Updates: posts on your site, found on Google and easy to share on WhatsApp.
  • A photo gallery.
  • Messages from your site's form reach your admin and your email, with follow-ups.
  • A WhatsApp button with openers in your own words: how to help, how to give, an event.
  • Gifts by UPI with a receipt: a supporter gives on your website by UPI and uploads the screenshot, you approve it in one tap, and a numbered receipt goes to them by email, with a PDF and a QR code anyone can scan to check it. Cash, cheques and transfers entered by hand. A list of every gift and receipt, and what you were given this month and this financial year on your dashboard.
  • Events listed: date, place, a map and a calendar link; the next three on your home page, past ones kept.
  • Your registrations in Settings: type of organisation, registered name, registration number, PAN, 80G number and validity, 12A, CSR-1, NGO Darpan ID, and FCRA with its bank account.
  • Social posts: an update or an event as a finished picture and caption, shared to your WhatsApp status from your phone.

Plans and prices

A community organisation has plans of its own and never sees the homestay plans. Prices are per year.

Plan Price per year What it adds over the plan below
Website ₹9,000 Everything in "What every site gets". 1 GB of storage.
Basic ₹12,000 80G receipts with your PAN and 80G number, the donor list and the yearly donor statement (Form 10BD) to upload; online gifts by card or UPI through your own Razorpay; event registration and attendance with a QR ticket; your own colours; 3 logins besides the owner.
Growth ₹15,000 Members and dues with membership types, receipts (or a tax invoice when you have a GSTIN), reminders and the overdue list, and a join form on your site; member cards with a QR that shows valid or expired; campaigns with a goal; monthly giving with a reminder and a pay link; volunteers and hours with a certificate; notices to members or donors who agreed, and on your site; a complaints or requests box with a reference and status emails; logins with roles: Secretary, Treasurer, Event desk, Volunteer lead. 5 logins and 3 GB of storage.
Plus ₹18,000 Your own domain, your site in 8 languages, Accounts: gifts and fees counted as income, your expenses, income and expenditure by month. 8 logins.
Pro ₹30,000 Alerts on your phone (a new gift, a new event registration, a new message). 20 logins and 25 GB. The premium Monsoon design. The AI helper: visitors type a question on your website and it answers from your own pages.

For a self help group: two plans of their own, outside the ladder above, paid by the year only.

Plan Price per year What it carries
SHG Books ₹1,200 The group's books: members, meetings with attendance, savings, the cash book, internal loans with schedules, bank loans, a passbook for each member and the grading sheet. A one-page website on the Rangoli design, 1 login for the book-keeper, 512 MB. Sell what the group makes in a basket on its site. No donations.
SHG Federation ₹20,000 For an NGO, a village organisation or a cluster federation: the books of up to 25 groups under one login (more by asking us), a page for each group that wants one on your website, and what the groups make in a basket. 5 logins and 5 GB.

For a temple or religious trust: the same five plans and prices, with what a temple needs on them. Any faith: a Hindu temple, a gurdwara, a church, a mosque or another place of worship, each in its own words.

Plan What it adds for a temple
Website Darshan and aarti timings: summer and winter hours, the daily aarti list, festival days and closures, and the today line on your website. Live darshan, rules for visitors, your temple's story, gifts by UPI with plain receipts
Basic Sevas offered online in time slots, paid first, with a seva slip and a receipt of its own; the pujari's list of the day's sevas and a pujari login; prasad by post to any country at the postage you set, with a tracking number. The hundi count and a register of gifts in kind
Growth Annadan or bhandara sponsorship with a calendar of open dates
Plus Hundi counts and seva offerings in your Accounts

GST. Plan prices are what you pay. StayCraft is not GST-registered, so no GST is added.

Add-ons. None. Everything is on a plan.

How paying works. No free trial and no card up front. We agree the plan and the price first. Payment is by UPI or bank transfer, the screenshot is uploaded in the Billing screen, and the plan is switched on the same day.

Features in detail

Donations and receipts

Giving on your website. A Give page (/donate), and the same form on your home page in the Lantern design. A supporter picks an amount (₹500, ₹1,000, ₹2,500, ₹5,000 or their own), gives their name, email or phone and address, and what the gift is for. They tick I am an Indian citizen: the law does not let most organisations take gifts from foreign citizens, so a supporter who is not one is shown your FCRA bank account if you are FCRA registered, and told you cannot accept the gift if you are not. Nobody pays online from abroad.

How the money comes.

  • UPI with a screenshot (every plan): your UPI ID and a QR code for the amount, then the screenshot. You check the money is in your account and press Money received; the receipt goes at once.
  • Online by card or UPI (Basic and above): paid into your own Razorpay account, never StayCraft's. The receipt goes the moment the payment is captured, and never before.
  • By hand: Record a gift for cash, a cheque, a bank transfer or a UPI payment you can see. The receipt is numbered and sent in the same step.

Receipts. Numbered by financial year from 1 April: DON/26-27/0001 for a plain receipt and 80G/26-27/0001 for an 80G receipt. A PDF with your registered name, registration number, PAN and 12A, the donor's name and address, the amount, the mode and the date, and a QR code to a page where anyone can check the receipt is genuine (it shows the number, your name, the amount, the date and the donor's first name; never a PAN or address). Sent by email; download it or send it again from Giving › Receipts. A refund cancels the receipt: it keeps its number, stays on record and its check page says it was cancelled.

80G receipts (Basic and above). A supporter ticks I want an 80G receipt and gives their PAN (checked as it is typed). The receipt then carries your 80G number and its validity and the donor's PAN. An 80G receipt is issued only when everything is in place: your PAN, 80G number and both validity dates saved in Settings, the gift's date inside them, the donor's PAN, and the gift not cash above ₹2,000. Otherwise a plain receipt goes, and you are told why on the gift's line and in your email.

Donors (Basic and above). One line a donor: what they gave this year and in all, their last gift, and their PAN masked. Remove details removes a donor's phone and email when they ask; their name, address and PAN stay, because the receipts and the tax return need them.

Form 10BD (Basic and above). Giving › 10BD export gives the year's statement of donations as the CSV the income tax portal's upload takes: one line per donor and way of giving, from your 80G receipts, cancelled ones left out. Due by 31 May.

Events

  • An event page for each camp, drive or meeting: what happens, when, where (with a map link), an online link if it is online, a photo, and Add to calendar.
  • Every plan lists events. On the Website plan an event page says Message us in place of a form.
  • Registration (Basic and above): name, phone, email and how many people. A free event's ticket comes at once.
  • Places: set a number and registration closes by itself when they are taken. Set a closing time, or switch registration off.
  • Paid tickets through your own Razorpay, or by UPI with a screenshot you approve. No ticket goes out before the money is in.
  • The ticket: a QR code and a code to type, on a private page and by email.
  • Attendance on a phone at the door: scan the QR with the phone's camera, type the code, or find a name or phone number, then Mark present. It counts present of registered.
  • Registrations list for each event, with filters, a CSV download, and Resend ticket.
  • Cancel an event and everybody registered is emailed.
  • A new registration rings your phone on plans with owner alerts, and so does a new gift; your dashboard shows the next event and how many registered.
  • Free registrations' names and numbers are cleared after 12 months, like other records; paid ones are kept as money records.

Your website: Lantern

  • The first screen is the opening of a short film about your cause: your video playing behind it if you turn that on, else your photo, slowly pushing in. One line of your mission in a large serif, your name and town above it, three of your own numbers counting up, and a marigold Donate button. Deep ink indigo, marigold and soft paper white.
  • Your sections, in the order you choose in Design: your story, Impact numbers (up to four, each a number, what it counts and a line), Programmes (each a photo, a name and a short line), Donate (your appeal and the ways to give), Events, Updates (your three latest), the photo gallery, Committee (name, role, term and photo, or their initials), Documents, Volunteer, where to find you and a Write to us form.
  • Your screens under Your website: Programmes, Committee and Documents. Drag to reorder; switch any one off the site.
  • Documents are PDFs up to 20 MB with a title, a kind (registration certificate, 12A, 80G, CSR-1, FCRA, annual report, audited accounts) and a year. Anyone can download one you show; one you switch off cannot be opened from your site at all.
  • Volunteers fill in their name, phone or email and how they can help. It arrives under Messages starting "Wants to volunteer", and you follow it up like any other message. On Growth and above it is the volunteer sign-up instead (below).
  • Your footer says what you are registered as, from Settings › Registrations, and your NGO Darpan ID: only what you typed.
  • Motion that is calm and slow: sections rise into view, numbers count, a warm glow follows the scroll. Visitors who ask for less motion, and anyone who prints the page, see everything still. In 8 languages for visitors.
  • No photos yet? The first screen draws the hills at dusk and each programme a numbered plate, until you add your own.
  • Its own touches, as on every organisation design: the Ask a question button (always at the bottom right) and the Write to us form are styled the design's own way, and a small hand-drawn mark of the design's own (a lantern here, a cricket ball on Pavilion, a deodar on Deodar) sits between the sections and draws itself in as a visitor scrolls. What they ask and do stays the same.

Members and dues

Growth and above. Under Members in the sidebar: Members, Fees and dues and Membership types.

Membership types. Each with its fee and how often it is paid: for life (once), every year, six months, three months or month, and a student or concession rate if you like. Start with the usual ones for your kind (a club: Life, Annual, Student; an RWA: monthly maintenance per flat; an NGO: Annual member) and change the fees. A type a member holds is never deleted: take it off the join form instead.

The register. Name, phone, email, photo (for the card), membership, member number (given when they are first active: M-0001), joining date, paid up to, and Waiting for approval, Active, Lapsed, Left or Not approved. An RWA also keeps the flat and owner or tenant. Under 18 (from the date of birth, or the "under 18" tick), a member cannot be saved or approved without a parent or guardian's name and their consent. Search by name, number, phone, email or flat; filter by status, membership and under 18. Nothing is deleted.

The join form on your website (/join, and a Join section for your home page): the membership types with their fees, name, phone, email, the flat for an RWA, the under-18 parent or guardian, and "send me the committee's notices" (off unless they tick it). It makes a request for the committee: you get an email, and Approve gives them a number and raises their first fee. Spam is dropped by a hidden field and a limit on how often one address can send, and an email address that can never receive mail is refused.

Dues. Raised by themselves on the day a member's period starts, counted from the day they joined, and never twice; a life fee once. Never reaching back before a member's first fee, so adding an old member does not bill them for past years. Raise a fee on a member for a one-off. Paid three ways: online through your own Razorpay (Basic's online payments), by UPI with a screenshot you approve, or cash, a cheque or a transfer you record. Waive (they stay paid up) or Cancel (raised by mistake); nothing is deleted. A member who pays online and closes the tab is found within minutes.

Receipts or tax invoices. Every payment gets a numbered PDF by email, MEM/26-27/0001, numbered by financial year from 1 April. With your GSTIN saved under Settings → Your business & GST, it is a tax invoice instead (MINV/26-27/0001): the fee read as including GST at 18%, CGST and SGST shown, SAC 9995. An RWA's maintenance up to ₹7,500 a month per member is exempt and says so.

Reminders and the overdue list. An email to the member with their pay link three days before a fee is due and three days after it is late, once each. Send on WhatsApp opens WhatsApp with the message and the link. Overdue fees are red, counted on the sidebar, and listed with the Overdue filter; the page says what came in this month and what is overdue. A membership not renewed 30 days after it ran out is marked Lapsed, and paying makes it active again. A member can also ask for their pay link on your site (/dues) with their number and phone: it goes to the email you have for them.

Member cards (Growth and above). A card to print or save as a PDF: photo, name, number, membership, valid until, and a QR code. Scanning it opens a page that says valid or not valid today, with your organisation's name and the member's first name, number and membership: nothing else. The code cannot be guessed and carries no phone or email.

Campaigns, monthly giving and volunteers

Growth and above. Under Campaigns in the sidebar: Campaigns, Monthly giving, Volunteers and Volunteer hours.

Campaigns. A cause with a goal: a title, the story (the posts editor), a cover and up to eight more photos, a start and an end date. Raised so far and the number of supporters count themselves from the campaign's gifts that have reached you (a gift waiting for its money, or refunded, does not count). Featured puts one first on your home page. Choose to stop taking gifts once the goal is met, or carry on to the end date. Each campaign has its own page (/campaigns/…) with a goal bar, the days left, the story and photos and Give to this campaign; /campaigns lists the open ones, then the past ones. A Campaign section for your home page shows the featured one. The gifts list shows each gift's campaign, with a filter, and Record a gift can give a cash or cheque gift to one.

Monthly giving. A supporter ticks Give this amount every month on your donate page (or opens /give-monthly), with their email and a tick for the monthly reminder. Nothing is taken from their account by itself: on the same day each month (the 29th to 31st fall on the 28th) they are emailed a link to give, never twice in a month, and each gift gets its receipt once it reaches you. From the link they give this month (online or by UPI), pause, resume or stop. Autopay (new, 5 Nov 2026): when you switch it on under Settings → Online payments (your Razorpay needs Subscriptions on), a supporter may instead approve once, by UPI AutoPay or card, up to ₹15,000 a month, and the gift reaches your own Razorpay each month by itself, receipted each time. They can stop it in their own UPI or banking app. You see every promise, active, paused or stopped, with what was given against it, and Send on WhatsApp sends this month's link.

Volunteers. A sign-up form (/volunteer, and the Volunteer section): name, phone, email, skills, when they are free (weekdays, weekends, evenings, events only) and a note. Under 18, a parent or guardian must give their name and agree. Each sign-up is New; mark them Active or Inactive. Hours are logged per event or for any activity. A certificate of hours for a period, signed by a member of your committee, as a PDF with a QR code that opens a page saying it is genuine (the organisation, the volunteer's first name and initial, the hours and the period).

Notices, roles, Accounts and complaints

Notices (Growth and above). Notices › Notices: write a notice or an appeal from a starting template (a meeting, a water or power cut, an appeal, a thank you), and choose who it goes to:

  • Members who asked for notices: active members who ticked "Send me the committee's notices" when they joined.
  • Donors who asked for updates: donors who ticked Send me your updates and appeals on the donate form. The box is off by default; a donor who did not tick it is never written to.
  • Both, one email a person, or nobody: a notice for your website only.
  • Before anything goes you see how many it reaches and who is left out (no email, unsubscribed). Send by email: every email has an unsubscribe link, and anyone who unsubscribes is never written to again. Send on WhatsApp: tap each person to open WhatsApp with the message written. A log shows who it went to.
  • Show on the website, and Pin to the top: your notices page (/notices), and the notice board of a design that has one, newest first with pinned ones on top. Take one down at any time.

Complaints or requests (Growth and above). A form on your site (/complaints, and the Complaints section of Your website): name, a flat or member number, a phone or an email, what it is about, an optional photo, and the privacy box. An RWA and a self help group call it Complaints, a club and an NGO Requests.

  • The person gets a reference to quote and a page that shows where it stands.
  • Members › Complaints (or Requests) lists them, newest first. Move each one Open → In progress → Done; the person is emailed each time. A note is for the committee only.
  • A photo has its location and camera details removed, and is opened from your admin only.
  • Done ones are cleared 12 months after they were last touched, like messages. Remove details clears one person's when they ask.

Logins with roles (Basic and above, by your plan's logins). People gives each login a role:

  • Secretary: everything but your plan and the logins.
  • Treasurer: gifts and receipts, donors, the 10BD export, members' dues and payments, monthly pledges, and Accounts.
  • Event desk: the Attendance screen only, to mark who came.
  • Volunteer lead: volunteers and their hours, and the events to read.
  • Book keeper (with SHG books): the self help groups' books only.

Accounts (Plus and above). Accounts opens as income and expenditure: confirmed gifts and members' fees and dues count as income by themselves (a gift waiting for its money does not), with any other income you enter (a grant, a hall hired out). Expenses, monthly expenses and their headings as for every business. One row a month, with a spreadsheet download.

Your website: Pavilion, for a club

A second design, made for clubs and associations, on every plan. Ground green, cream and brass; a slab serif for the numbers and the fixtures.

  • The first screen: your crest (your logo, or a shield with your initials and the year you were founded), your name, and a scoreboard whose tiles flip like a station board's: how many members you have, the day of your next event, and your own numbers. A tile with nothing true to show is left out: never "0 members". Under it, the next fixture, with a link to its page. On a laptop the scoreboard and the next fixture sit side by side in a band under your name.
  • Fixtures: your next three events as team sheets (when, where, free or the ticket price) that slide in as they come into view.
  • Membership and notices: a Become a member button with your member count, your current appeal with how much is raised, and your latest notices with the pinned ones first, and a link to send a request. Each part shows only when you have it.
  • Honours board: your past presidents (or captains, or champions), lettered in gold on a green board. You type the names in the section.
  • Your story, your numbers as a scorecard, your committee as brass nameplates, club news, your photo albums, the ground fund, your papers, where to find you and Write to the club with WhatsApp.
  • Visitors who ask their phone for less motion see everything still; it prints cleanly.

Demo: pavilion-demo, Ridge Sports Club, an invented cricket, walking and running club in Shimla.

For the team only. Views in resources/views/site/blocks/pavilion/, resources/css/pavilion.css, resources/js/pavilion.js (no library). Its own blocks honours and clubhouse (CommunityPage::PAVILION_BLOCKS), and a hero field founded. It reads the stage 2 modules only through CommunityBoard (members count, join, campaign, notices, complaint link), each left out while empty; club-demo stays on Lantern. The default design for every organisation stays Lantern.

Your website: Courtyard, for a residents' welfare association

A design made for residents' welfare associations, housing societies and colonies, on every plan. Warm stone, neem green and brick red; one friendly rounded sans throughout.

  • The first screen: your colony from above (your photograph, or a hillside of homes drawn until you add one), your name, and a notice board with your latest three notices pinned to it, the pinned ones first. They drop onto the board and settle with a little sway. Before you post notices, the board pins your latest three updates; with neither, there is no board. On a laptop the board runs across the page under your name, the notices side by side. Beside your name, Pay your dues (once you raise dues), Raise a complaint (once the complaints box is on) and This month's meetings.
  • Dues status: this period's dues, the day they fall due, the share of homes that have paid (only if you choose to show it) and a Pay button. Never a name or an amount per person. Shows only once dues are raised.
  • Meetings and events on a wall calendar open at the month, every event day ringed; last month's page turns as it comes into view. Beside it, the coming events with when, where and entry.
  • Useful numbers: the gate, the plumber, the electrician, the water office, the secretary: you type them in the section, and each is called with one tap.
  • Your story, your numbers, what you look after, your committee, your minutes and accounts, your photo albums, the join form, the festival fund, where to find you and Write to the committee with WhatsApp.
  • Visitors who ask their phone for less motion see everything still; it prints cleanly.

Demo: courtyard-demo, Sector 4 Residents' Welfare Association, an invented association in New Shimla.

For the team only. Views in resources/views/site/blocks/courtyard/, resources/css/courtyard.css, resources/js/courtyard.js (no library). Its own blocks contacts and dues (CommunityPage::COURTYARD_BLOCKS); it draws events as the wall calendar. It reads the stage 2 modules only through CommunityBoard (dues status, notices, complaint link), each left out while empty; rwa-demo stays on Lantern. The default design for every organisation stays Lantern.

Self help group: the group, members, meetings, savings and the cash book

On SHG Books and the SHG federation pack, under Self help group in the sidebar.

  • The group. A self help group's own site has its one group, made for it. An NGO, a village organisation or a cluster federation turns the books on in Settings › Registrations ("We keep the books of self help groups"), adds each group under Groups (up to its plan's number), and switches the group in view; every screen shows only that group's books.
  • Members. Each with her number in the group, her name (and in Hindi), her role (member, president, secretary, treasurer), her nominee and the day she joined. A group usually has 10 to 20: outside that the screen reminds you, and never refuses. A member who leaves is marked Left; her books stay.
  • The meeting sheet. One screen per meeting: the date, who came, who was away or on leave, each member's saving (the group's fixed amount filled in), an expense, a fine or cash taken to the bank, the loans asked for and decided, and the minutes in the group's own words. Saving it writes attendance, each member's savings and the cash book together. A meeting is corrected, never rewritten: the old entries stay, crossed out, beside the right ones, with the reason.
  • Savings ledger. Each member's savings line by line with her running total, and who is behind, the most owed first.
  • Cash book. Cash in hand and money in the bank, the opening balance from the paper book, money taken to or from the bank, and a reversal for a wrong line (never deleted). Month by month: at the start, in, out, and at the close.
  • Book keeper. A login for the person who writes up the books: every self help group screen, and nothing of the organisation's own (no plan, logins, gifts or accounts). She adds no group and deletes no line.
  • On your website, as totals only and only if you want: members, meetings held, savings together. Never a member's name or amount.

Self help group: loans, bank linkage, the passbook and the grading sheet

On SHG Books and the SHG federation pack, under Self help group in the sidebar.

  • Loans to members. Amount, purpose, interest a month (1% or 2%, or any rate), the number of instalments, monthly or at each weekly or fortnightly meeting. The schedule is worked out for you, and the formula is said in plain words: "₹10,000 at 1% a month, flat: ₹100 each time, ₹1,000 in all".
  • Flat or reducing. Flat (interest on the whole loan each time) is the default, as most paper books keep it. Reducing charges interest only on what is still owed: the same part of the loan each time, or the same amount each time (EMI). Each instalment is rounded to the rupee, and the last takes the difference, so the totals match your book.
  • The schedule is yours. Change any row to match the paper book; the loan parts must still add up to the loan.
  • Repayments at a meeting or by hand: interest first, then the loan. A part payment leaves the rest due. Paying extra shortens a flat loan or makes a reducing loan's instalments smaller. Close early, Write off, and an Overdue list. Penal interest is a group setting, off unless you turn it on.
  • Bank loans and funds. A cash credit limit (CCL) or a term loan: the sanction, each drawdown, each repayment with its interest, and whether it is regular. The revolving fund and community investment fund, and repaying a CIF.
  • Into the cash book by itself. Every loan, repayment and bank movement is written into the group's cash book. No money moves through StayCraft: the books are a record of what the group handled.
  • Passbook. Each member's savings, loans and repayments on an A5 page that looks like the paper passbook, in Hindi or English, to print or send her.
  • Grading sheet. The figures a bank asks for when it grades the group: meetings held against meetings due, attendance, savings regularity, loans to members, loan repayment, books up to date, and the bank loan's standing, each explained in one line, ready to print.

For the team only. Lane L2 of stage 3 (docs/designs/community-stage3-contract.md). The maths is App\Services\ShgLoanSchedule (pure, tested against hand-worked passbooks); ShgLoans, ShgBankLinkage, ShgPassbook, ShgGrading. Hindi passbooks are printed by the PDF service (Gotenberg, collateral.pdf_url); without it they come in English. rangoli-demo carries loans, a CCL and the RF from its blueprint's shg key.

Self help group plans, many groups, and selling what the group makes

  • SHG Books, ₹1,200 a year: one group's books, its one-page website, one login for the book-keeper.
  • SHG Federation, ₹20,000 a year: one login keeps the books of up to 25 groups. Pick a group, then its books. At the limit, Add a group says so; ask us on WhatsApp for more.
  • A page for each group on a federation's website, at /groups: its name in Hindi and English, its village, the year it began saving, its own words, its photo and its totals (saved together, lent to each other, members, meetings), only once the group is marked published. Never a member's name, phone or money.
  • What the group makes, sold: pickles, socks and shawls under Local crafts › Products, on the site with a basket. Buyers pay the group by UPI with a screenshot, or through the group's own Razorpay; you approve each order under Local crafts › Orders. This is the group's trade, kept apart from its books.
  • WhatsApp openers on an SHG site ask about the group's products, how to join a group and when the group meets.

Your website: Rangoli, for a self help group

A design made for self help groups, on every plan and on SHG Books. Terracotta, turmeric and leaf green on cream; Baloo 2 and Mukta, so Hindi reads as naturally as English. Made for a phone.

  • The first screen: your group's photo at the heart of a chalk kolam that draws itself, dot by dot and line by line, your name in Hindi above your English name, and Saving together since the year you began. Your group's profile fills them in when you keep your books here; otherwise you type them in the section.
  • Savings together: what your members have saved and lent each other, from your books, opening out from a turmeric centre like a rangoli. Group totals only, never a member's name or amount, and only if you have not hidden your figures.
  • Our meetings: how many members you are and how many meetings you have held, with your own line about when and where you meet.
  • What we make: your products as a strip a visitor can order from, once you sell through your website.
  • Your story, what you make, your events, news, photographs, where to find you and Write to us with WhatsApp. No Donate button: your main button opens WhatsApp with your group.
  • A figure with nothing true to show is left out: never "₹0 saved". Visitors who ask their phone for less motion see everything still; it prints cleanly.

Demo: rangoli-demo, Saanjh Mahila Swayam Sahayata Samooh, an invented group of fourteen women near Palampur.

For the team only. Views in resources/views/site/blocks/rangoli/, resources/css/rangoli.css, resources/js/rangoli.js (no library). Its own blocks savings, meetings and basket (CommunityPage::RANGOLI_BLOCKS), and hero fields local_name and since. It reads the books only through ShgBoard (group, members, meetings, savings, loans) and the SHG products partial, each left out while empty; shg-demo stays on Lantern with no books. The default design for every organisation stays Lantern.

Your website: Monsoon, the premium design

A premium design, on Pro, made for NGOs that raise money for a campaign: flood relief, a relief fund, a building fund. Slate, rain-blue and wet-leaf green, with one coral for Donate; a tall condensed sans over an easy one to read.

  • The first screen: your photograph seen through a window in the rain. Drops run down the glass and bend the picture behind them; as a visitor scrolls, the rain eases off and your photograph sharpens. Your mission in tall capitals, and one coral Donate button.
  • Your appeal under it: your featured campaign, what you have raised so far, your goal and the days left, with a rain gauge that fills like water rising. With nothing raised yet it shows your goal and "Be the first to give", never 0%; with no campaign, your mission and Donate alone.
  • The appeal section: the campaign's story and what the money does, a tall rain gauge and Give to this appeal.
  • Your mission, your programmes as panes of a window, your numbers counting up, how to give, your updates, your photo albums, your documents, where to find you and Write to us with WhatsApp.
  • Phones that cannot draw the rain smoothly, and anyone who asks for less motion or saves data, see a still window instead, and it prints cleanly. Keep the first screen still shows the still window to everyone.

Demo: monsoon-demo, Beas River Foundation, an invented river trust in Kullu with a flood relief appeal.

For the team only. Views in resources/views/site/blocks/monsoon/, resources/css/monsoon.css, resources/js/monsoon.js (raw WebGL, no library: one fragment shader that refracts the hero photo). Premium (premium_designs), gated as Rath and Nitro. Its own block appeal (CommunityPage::MONSOON_BLOCKS) and a hero field still_rain. It reads the campaign only through CommunityBoard::campaign(). monsoon-demo is on Pro (its blueprint's plan). The default design for every organisation stays Lantern.

Temples and religious trusts: the preset and its words

On every plan. Sign up, or switch under Settings → Registrations, as a Temple or religious trust, then pick the faith:

Faith The words the site and the admin use
Hindu temple temple, pujari, seva, aarti, prasad, darshan, annadan, hundi; "Offer a seva", "Live darshan"
Gurdwara gurdwara, granthi, sewa, path and kirtan, karah prasad, langar, golak; "Offer a sewa", "Live kirtan"
Church church, priest, service and Mass, a blessed offering, a community meal; "Request a service", "Live service"
Mosque mosque, imam, khidmat, namaz, a community meal; "Offer khidmat", "Live from the mosque"
Another place of worship neutral words: religious leader, service, prayer, offering

Every faith has the same features; only the words change. A devotee is never asked to "book" anything.

  • The WhatsApp button asks in the faith's words: Ask about seva timings, Ask about prasad by post, Ask about darshan (a church: Mass timings, a service, a visit; a mosque: namaz timings, khidmat, a visit). In all eight languages.
  • Run by the state temple trust? A temple managed by the Commissioner or the Deputy Commissioner (the HP Hindu Public Religious Institutions and Charitable Endowments Act 1984) may sign up. It is reminded on its dashboard, in Settings and on the plan page that it may need the DC's approval before it takes money online. Nothing is blocked.
  • 80G for a temple (Basic and above): off until the trust saves its own 80G number and ticks that its CA has confirmed it covers these gifts. A temple notified under 80G(2)(b) gives 80G receipts only on gifts to its repair fund (a campaign it chooses), within the notification's date and cap, and the receipt names the notification. Every other gift gets a plain receipt.
  • Watch live: a section with the temple's YouTube stream or a video, played without YouTube's cookies until pressed. YouTube only.
  • Rules for visitors: a section with what to wear, photographs, footwear and timings, each with an icon, and more lines of the temple's own.
  • A Hindu temple starts on the Deodar design, every other faith on Lantern.

For the team only. Gate App\Support\Temple (preset worship), words in config/temples.php (faiths, openers; the neutral choices noted there for Arun to review with someone of each faith), App\Support\TemplePreset (settings, warning, openers, signup), App\Support\Temple80g (wired into DonationReceipts::offered() and eightyGBlocker()), App\Support\TempleLive (the live block's link). Signup keeps worship_faith and worship_state_run on signup_requests. The 80G and legal questions are in docs/ops/ca-brief-80g-and-gst.md, Part C.

Temples: lending the hall

Basic and above (it rides on sevas). Settings → Registrations → Lend our hall to devotees turns on a Halls page on the website and a Halls group in the admin. A hall has a charge, a deposit that holds a day, the parts of the day it is lent in, notice, how far ahead, and festival days it is not lent. A devotee asks for a day (asking holds nothing); the temple approves (the day is held, the deposit asked for) or declines; the deposit is paid online through the temple's own Razorpay or by UPI with a screenshot the temple checks; then it is confirmed. Two reservations never hold the same hall, day and part of a day. The temple returns a deposit itself and notes it.

For the team only. App\Services\HallBookings, Hall, HallBooking, HallController, HallResource, HallBookingResource, Temple::halls() (sevas plus the hall_bookings setting; no plan key yet: add one later without moving a table). Tenant tables halls, hall_bookings (migration 2027_01_23_000101). Approval and the deposit's recording check clashes under a lock on the hall's row. Backup download-only and in the export. No owner phone alert yet (email only). Docs: docs/ops/temple-halls.md.

Temples: sevas, timings and prasad by post

For a temple or religious trust (the preset), in the faith's own words: a gurdwara's sewa, a church's service.

Timings (every plan):

  • Darshan hours for summer and for winter, each switched on by a date you set (1 March and 1 November unless you change them). One or two sittings a day.
  • The daily aarti and pooja list: name, the name in Hindi or your script, the time and the kind.
  • Special days: a festival with its own hours and its own list, or a day you are closed (an eclipse) with the reason. No seva is offered on a closed day.
  • On your website: a today line ("Temple open · Sandhya aarti 6:30 pm"), and the Timings and Aarti schedule sections, the next aarti marked.

Sevas (Basic and above):

  • Seva types: the offering, fixed or as the devotee wishes from a least amount (or free, such as a darshan pass); the days of the week; fixed times, or any time in the day; how many at each time; how far ahead; how much notice; days it is not offered (festival days); gotra asked or not; what to bring; a photo.
  • A devotee offers a seva on your website: the day and time, their name, gotra (optional), the names it is offered for, how many will come, phone or email.
  • They pay first, online through your own Razorpay or by UPI with a screenshot. Their place is held for 30 minutes while they pay; a screenshot keeps holding it until you approve it.
  • A time never takes more than its places: if the last place goes while somebody pays, you are told, to move them or return the money.
  • Once the money is in: a seva slip by email with the time and what to bring, and a receipt of its own (SEV/26-27/0001, a PDF with a QR anyone can check). Never a donation receipt, never 80G.
  • Sevas: every slip, with its payment; approve a screenshot, record cash at the counter, cancel (the slip is kept).
  • Today's sevas: the pujari's list, today only, by time, each devotee's name and gotra in large type, a Done button, printable on A4.
  • A Pujari login: Today's sevas and To post only, never the money.
  • The Offer a seva section on your website: your sevas as cards with the next open time.

Prasad by post, to any country (Basic and above):

  • A seva can offer prasad by post. The devotee gives an address in any country you post to.
  • Postage: one line per country, a Rest of the world line, and countries marked not posted to. With neither, the form says prasad cannot go there.
  • The postage is added to what the devotee pays first, and shown apart on the receipt.
  • To post: the address and country; mark it posted with the tracking number, and the devotee is emailed.
  • Cards from abroad work once international payments are switched on in your own Razorpay. Food sent abroad meets the customs rules of the country it goes to.

For the team only. Tables seva_types, seva_slips (the receipt number on the slip), prasad_posts, postage_rates; timings are the temple_timings settings row (App\Support\TempleTimings). Slot maths in App\Support\SlotRules (lifted from ReservationRules, which shares its time parsing). The money path is App\Services\SevaSlips (EventRegistrations' pattern: lock the seva type, then the slip); paidBetween() feeds Accounts (lane L3). Pages /seva, /seva/{slug}, /seva-slip/{token}, /seva-receipt/{code}. Blocks timings, schedule, seva (the contract's today is Lobby's). A paid slip is a money record, kept after the 12-month clear-out; a posted prasad's address is cleared.

Temples: hundi count, gifts in kind and annadan

A new Offerings group in a temple's admin, in its faith's words (a gurdwara's golak and langar).

  • Hundi counts (Basic and above). Each opening of a hundi is written down: the day, which hundi, who counted and who checked (two different people, both named), and anyone else present. Enter how many of each note (₹2,000 down to ₹10) and coin (₹20 down to ₹1): the total is worked out to the paisa and the count is confirmed only when it matches the total written on the signed sheet. A photo of the sheet can be kept with it, and the sheet printed for signing.
  • Foreign money in a hundi is written down on its own (currency, amount, your own estimate in rupees), with the note that it may be a foreign contribution under FCRA and to ask your CA before banking it. It is never added to the rupee total, and reaches your accounts only once you mark it banked on your CA's advice, at the rupees credited.
  • Locked once confirmed. A mistake is fixed with Correct: a reversal of the count and a new count to confirm. The original stays on record; nothing is ever deleted. Mark a count banked with the day, the bank and the deposit slip number.
  • Gifts in kind (Basic and above): a simple register, not stock. Gold and silver by weight in grams, cloth, grain and anything else by quantity, who gave it (or nobody named), and what became of it (kept, used, auctioned, given away). A giver can have a plain acknowledgement numbered INK/26-27/0001; goods earn no 80G, so it never says 80G. A rough value can be noted for your own record and is never counted as income. The register prints, with gold and silver totals.
  • Annadan or bhandara sponsorship (Growth and above): set what one costs (for the day, or per meal with the sponsor choosing how many), how many sponsors a date takes (one, or several), how far ahead and on which days of the week dates open, and the days you close (with the reason). Devotees choose a date from the calendar on your website, write who it is in memory of or for, and pay you directly, online through your own Razorpay or by UPI. Each sponsorship is a gift: the same numbered receipt, and 80G only where your temple's 80G allows it.
  • Paid first. A date is taken only once the money reaches you. If two sponsors pay for the last place at once, the first keeps it and you are shown the other to move to another date or refund. A sponsor's name shows on the calendar only if they tick that they agree. The Annadan calendar section shows the coming dates on your home page.
  • Accounts (Plus and above): the hundi counts and seva offerings are income beside gifts and members' fees, month by month, against your expenses. Gifts in kind are noted apart, never as money.
  • Your treasurer keeps the hundi counts, gifts in kind, annadan and the accounts; your secretary the annadan. The pujari sees none of them.

For the team only. App\Services\HundiCounts, GiftsInKind, Annadan; tables hundi_counts, hundi_count_lines, gifts_in_kind, annadan_dates, and donations.purpose / for_date (with dedication, name_shown, meals). Screens HundiCountResource, GiftInKindResource, AnnadanPage (group Offerings); pages /annadan, /annadan/{token}; prints under /admin/offerings. Accounts through CommunityAccounts::hundi(), ::sevas() (L2's SevaSlips::paidBetween()), ::inKind(). Never cleared: hundi counts and gifts in kind (a giver's name is blanked after the retention period). The FCRA line is in config/community_receipts.php for the CA.

Your website: Deodar, for a temple

A design made for Hindu temples and temple trusts, on every plan, the Himachali kath-kuni way: deodar wood and slate, vermilion for the one button that matters, marigold and brass, on snow white. Headings in Tiro Devanagari Hindi, so your name reads as well in Hindi as in English. A new Hindu temple starts on it; every other faith starts on Lantern, and may pick Deodar too (its words follow the faith: a gurdwara's says "Offer a sewa").

  • The first screen: two carved deodar doors swing open on your temple at first light. Your name in Hindi above your English name, today's line ("Temple open · Sandhya aarti 6:30 pm"), and two buttons: Offer a seva and Give. On a festival day a string of marigolds hangs across the top.
  • The bells: the day's aarti and pooja run down the page as brass bells on a rope, each swaying as it comes into view, with a diya burning beside the next one due and what is over dimmed.
  • Timings: today's darshan hours on a carved panel, the week's below, summer or winter, a closed day with its reason.
  • Sevas: each with its offering (₹1,100; "as you wish, from ₹501") and its next open time, and Offer a seva.
  • Next festival: your next jatra, festival or bhandara from your events, with its dates and place.
  • Annadan: the price of a day's meal, the coming dates open or sponsored, and the sponsor button (Growth and above).
  • Live darshan, rules for visitors, your history, how to give, your photo albums in carved frames, your committee and documents, How to reach (the road, the nearest bus stand and the walk up), the map and Write to us.
  • Every section with nothing to show is left out: never "₹0". Anyone who asks for less motion sees the doors open and the bells still; it prints cleanly. Keep the doors open shows them open to everyone.

Demo: deodar-demo, Sarikhol Devta Mandir Samiti, an invented devta temple committee above Banjar, Kullu.

For the team only. Views in resources/views/site/blocks/deodar/, resources/css/deodar.css, resources/js/deodar.js (CSS 3D and IntersectionObserver, no library). Standard, themeable. Its own blocks festival and reach (CommunityPage::DEODAR_BLOCKS), hero fields local_name and doors_open. It reads the temple only through TempleBoard and the temple partials (temple-today), each left out while empty; Temple::defaultDesign('hindu') is deodar. The demo's photographs are other Kullu and Mandi temples, captioned only with what they show.

What it does not do yet

  • No gifts from abroad online: an organisation registered under FCRA shows its FCRA bank account instead (D3).
  • No monthly giving by card subscription: a monthly reminder with a pay link instead (D5 A, stage 2).
  • Not listed in the StayCraft directory.
WhatsApp us