Skip to content
PresencebyAnimweb Technologies

Plans and pricing explained

The three tiers and what each includes, why the price depends on the number of students, one-time charges, the security deposit, deployment options, what is not included and when payment is due.

9 min read

All prices are in Indian rupees, per month and before GST. Each price is a planning allowance: it covers the infrastructure sized for the tier, together with the Presence software, updates and support. The final amount is confirmed when your configuration and contract are finalised, and it may vary if your institution has additional requirements.

The tiers

Tier Active students (peak) Price per month Planned load Burst test
Tier C up to 15,000 ₹3,50,000 (₹3.5 lakh) 500 requests per second 1,500 requests per second
Tier B up to 25,000 ₹5,00,000 (₹5 lakh) 833 requests per second 2,500 requests per second
Tier A up to 40,000 ₹10,00,000 (₹10 lakh) 1,333 requests per second 4,000 requests per second

A free 7-day trial (one class of 30 to 40 students with their teachers) is available before you sign up - book one. For a price for your institution, request a quotation.

Proposed starting configuration

Tier C - 15K peak

  • 3 × Railway API servers (4 vCPU / 16 GB each)
  • MongoDB Atlas M40
  • Railway Redis (5 GB memory)
  • 1 × background worker (2 vCPU / 4 GB)
  • Railway Pro workspace
  • Cloudflare DNS/CDN and a Workers Paid allowance
  • Reserve for bandwidth, monitoring and variable charges

Tier B - 25K peak

  • 5 × Railway API servers (4 vCPU / 16 GB each)
  • MongoDB Atlas M50
  • Railway Redis (10 GB memory)
  • 2 × background workers (2 vCPU / 4 GB each)
  • Railway Pro workspace and Cloudflare
  • Reserve for bandwidth, monitoring and variable charges

Tier A - 40K peak

  • 8 × Railway API servers (8 vCPU / 32 GB each)
  • MongoDB Atlas M60
  • Railway Redis (20 GB memory)
  • 3 × background workers (4 vCPU / 16 GB each)
  • Railway Pro workspace and Cloudflare
  • Larger reserve for bandwidth, monitoring and variable charges

The configuration is a starting point. It is adjusted after load testing with your timetable, within the tier’s allowance.

What the parts are

Part What it does
API servers The servers that check every attendance request, run the leave and campus workflows and push live updates to teachers. Several servers share the load and keep the service running if one fails.
MongoDB Atlas cluster The managed, replicated database. Your institution has its own separate database in it. Larger cluster sizes handle more simultaneous reads and writes.
Railway Redis A fast in-memory store that keeps live class rosters and rate limits consistent across all API servers.
Background workers Run scheduled jobs away from the API servers: closing classes that have ended, checking out students who have gone offline, calculating final attendance statuses, and housekeeping. With several workers, they take turns so no job runs twice.
Railway Pro workspace The hosting account features a production service needs: team access, private networking between the servers, more replicas of each server, static outbound IP addresses and 30 days of logs.
Cloudflare DNS, the content delivery network that serves the app and website quickly across India, and edge protection.
Reserve Covers bandwidth, monitoring, backups and other charges that vary month to month.

What counts as an active student

Only active student accounts count towards the tier. Teachers, mentors, deans, administrators and campus staff are free and unlimited. Deactivated and graduated students do not count; their records are kept.

Why the price depends on the number of students

Presence checks every student continuously during a class, not only once:

  • every phone in a live class sends a signed location update to the server about once a minute, and every 15 seconds while it is outside the room or unsure (tiers are sized for the faster rate);
  • most students join in the first two minutes of a period, so the start of each period is a burst;
  • teachers watch a live roster that updates in real time.

The planned load is the steady load the tier is planned for, and the burst test is the load each configuration must sustain in testing - three times the baseline, so the start of a period and every student in class at the same moment are covered:

Tier Peak students Location updates per second if all are in class at once Burst test
Tier C 15,000 about 1,000 1,500
Tier B 25,000 about 1,667 2,500
Tier A 40,000 about 2,667 4,000

One-time charges and deposit

Item Amount (before GST) Notes
Complete customisation and setup ₹50,000, one-time Presence customised completely to your university’s needs - structure, roles and titles, offices, policies and workflows, with your name and logo on the app, its home-screen icon and the sign-in page - and set up ready for use. Takes about one month.
Security deposit for the main source code ₹1,00,000, refundable Taken separately from the tier fee. See below.

Security deposit rules

  • The deposit is returned only when the contract tenure ends.
  • If the contract is ended before its agreed end date, the deposit is not returned, whichever party is at fault.

Deployment options

Animweb-managed cloud (standard) Your own server and database
Where it runs The configuration listed for your tier, managed by Animweb Servers and a database your institution provides
Your domain Our app address, or your own domain Your own domain
Server and database costs Included in the tier price Paid by your institution
Backups Included, daily, with point-in-time recovery Your IT team
Fee Tier price Tier price +20%, plus a one-time installation fee of ₹49,999

Either way, the service is set up in the same eight steps - database, servers, app, Sign in with Google, email, first-run setup and checks before go-live - with no built-in passwords or sample data. See Setting up a new campus, step by step.

Using your own server and database

Some institutions must keep data on their own infrastructure. Presence supports this:

  1. You provide the servers (on campus or in your cloud account), the database and network access, following the technical requirements.
  2. We install and harden Presence, connect it to your database, and restore your demo workspace if you have one.
  3. We deliver updates and support remotely under a signed license.

The fee is 20% higher because installation, updates, troubleshooting and performance tuning then depend on infrastructure we do not operate. The one-time fee covers installation, security hardening and a handover session for your IT team.

Advanced Security add-on

For institutions that want a managed security service on top of the built-in protections. It is priced according to the agreed scope and includes:

  • 24x7 security monitoring and alerting for your deployment.
  • Web application firewall and DDoS protection rules tuned to your traffic.
  • Quarterly vulnerability assessment and penetration testing (VAPT), with a report and a re-test after fixes.
  • Security incident response, including help with reporting to CERT-In within the required six hours.
  • A monthly security report and a review of who has administrator access.

Every tier, with or without the add-on, already includes encryption in transit, a separate database per institution, two-factor sign-in for administrators, signed location updates, audit logs and the protections listed on the Security page.

Not included in any price

  • GST, added at the applicable rate and shown on your tax invoice.
  • Domain name registration and renewal. If you want Presence on your own address, your institution buys and owns the domain. Most institutions use a sub-domain of the domain they already have (for example attendance.your-university.edu), which costs nothing extra. See Using your own domain.
  • Requirements beyond the agreed customisation, such as integrations with other software or extra environments, priced separately.
  • Server and database costs when you choose to run Presence on your own infrastructure.

Complete customisation and setup

Every university is organised differently. For a one-time ₹50,000 (before GST), Animweb Technologies customises Presence completely to your university’s needs and sets it up ready for use. It takes about one month from the signed contract.

Week What happens
1 Requirements workshop with your administration: schools and departments, programmes and terms, roles and titles, offices, attendance, leave and fee rules, library rules, deployment option, domain and network details, privacy notice
2 Configuration: your name and logo, how people sign in (ID and password, and Sign in with Google with your email domain), campus boundary and maps, academic structure, names and titles, offices and their permissions, policies, Examinations, placement cell, HR, library, accounts and service desks; gate kiosks paired
3 Data and devices: staff and students imported from your lists, mentors, subjects and teachers mapped, desks and departments given their people; app installation drive, phone registration and staff face enrolment
4 Pilot in one department, corrections, training for administrators, heads, teachers, departments and desks, then go-live for all departments, followed by two weeks of priority support and a review meeting

Nothing you set up in your demo is lost: the customisation builds on it. What your institution provides, and everyone’s first sign-in, are set out in Setting up a new campus, step by step.

Payment

  • Payments are due only after everything is finalised: the scope, the configuration and the contract.
  • Payment is only by bank transfer (NEFT, RTGS or IMPS) against our GST tax invoice. We do not take online payments.
  • Your plan is activated within one business day of the funds reaching us.
  • Renewals: we send a renewal invoice before your term ends. Nothing is ever charged automatically. To not renew, tell us before the term ends; access continues until the end of the paid term.
  • Terms of 1, 6, 12 or 24 months are available. When you change tier, the time you have already paid for is converted at the new tier’s price, so nothing you paid for is lost.
  • More students than your tier allows: new students cannot be added until you move to a larger tier; existing students keep working.
  • The demo converts in place: users, classes, attendance and settings stay as they are.
  • Refunds: see the Refund & Cancellation Policy.