TurtleDock

Four kinds of institution. One record each.

TurtleDock builds a separate product for schools, for colleges and universities, for coaching institutes, and for students preparing on their own. Each has its own data model and its own records — and inside each, nothing is exported from one desk to be re-typed at the next.

Book a demo Which product is mine?
Written by Checked by MuthuLast reviewed
Four customers · four first screensSCHOOL · 07:52
SchoolDeck/Greenfield Sr. Secondary / Attendance / IX-B · P1offline · synced 08:07
Register · 38 students · 07:52Submit register
NoStudentTodayTerm
01Aarav DeshmukhPresent96.4
02Ananya RaoPresent94.1
03Dev Malhotra · 3rd dayAbsent78.1
04Fatima SheikhPresent98.2
05Ishita BoseLate 08:0491.0
Third consecutive absence — the parent was messaged at 08:05 without anyone remembering to. The same row feeds fees, marks and the report card.schools & school groups
Schools · SchoolDeckColleges · CampusHubCoaching · TutorDeskStudents · ExamEdge24 modules · one platformOffline attendance & feesRazorpay · Tally · WhatsApp · DigiLockerLive in three weeksSchools · SchoolDeckColleges · CampusHubCoaching · TutorDeskStudents · ExamEdge24 modules · one platformOffline attendance & feesRazorpay · Tally · WhatsApp · DigiLockerLive in three weeks

Four products. Pick the one shaped like you.

A school, a college, a coaching centre and a student each get their own product, their own data model and their own records. None of them is a “module” of another.

For schools & school groupsEvery classroom, every parent, one student record.Admissions through report cards, attendance period by period, fees that reconcile to the rupee, and a parent app that gets opened rather than uninstalled.
Explore SchoolDeck From ₹120 per student per year
Size band200 – 5,000 on roll; groups to 40 campuses
StructureClass → section → subject → period
Busiest deskFront office, 7:30–9:00 every morning
BoardsCBSE, ICSE, state, IB — formats configured, not coded
Modules on14 of 24
Live in2–3 weeks; 4–6 for a group
The first screen. The principal opens one page at 07:40: absentees, fee position by class, staff on leave, sections behind on marks.

Four separate products. One platform underneath. Never one shared database.

Between products, nothing is shared. A school’s records live in SchoolDeck, a college’s in CampusHub, a centre’s in TutorDesk, a student’s in ExamEdge. Different customers, different data models, no common student table.

Inside a product, everything is. Attendance, fees, marks and messaging write to one row per person — so nothing is exported from one desk to be re-typed at the next. Switching a module on is a permission change, never a migration.

Underneath, the engineering is common. Infrastructure, permissions, audit, payments and messaging are built once and hardened for all four.

How the 24 modules divide across the four
Four calendars

Each customer has a week that breaks software.

Schools, colleges, coaching centres and students run on different calendars, and each has a stretch where a slow system gets abandoned. Every product is engineered for its own peak.

APRMAYJUNJULAUGSEPOCTNOVDECJANFEBMAR
Schools · SchoolDeckAdmission rush Feb–Apr; results & report cards Mar
Colleges · CampusHubRegistration Jul–Aug; results fortnight Dec & May
Coaching · TutorDeskEnquiry season Mar–Jun; weekly test series all year
Students · ExamEdgeCountdown to JEE / NEET, Jan–May; mocks every week
Every institutionInstalment day 1–5 of each month; gateway load, receipts on confirmation
7:40–9:10School attendance peak. Registers never wait on a fee rush — the two are capacity-planned separately.
Results fortnightCollege releases frozen; a named engineer on standby while the controller clears departments.
400 enquiriesA coaching centre’s March. Follow-up that survives it, sorted by who is going cold.
142 daysA student’s countdown. Practice on the phone at 9 pm, offline on the train, revision that returns on schedule.
The platform underneath

Built once. Hardened for all four.

Infrastructure, permissions, audit, payments and messaging are engineered once and hardened for all four products — shared code, not shared data. Student data is the most sensitive data an institution holds; these are the defaults, not a tier.

99.9%
uptime, in the contract with service credits
30 min
response when fees or results are blocked
PermissionsPer field, per role, per branch. A class teacher never sees another branch’s ledger.
AuditImmutable log of marks, fees and attendance edits: user, time, before, after, reason.
EncryptionTLS 1.2+ in transit, AES-256 at rest, field-level for Aadhaar and bank details.
PaymentsRazorpay, PayU, UPI, net banking. Reconciled nightly to Tally and Zoho Books.
MessagingWhatsApp Business and DLT SMS from your number. Credits at cost, no margin.
OfflineAttendance and fee collection keep working without a signal and sync when it returns.
IdentityGoogle Workspace, Microsoft 365, SAML 2.0. OTP for parents and students.
ExportComplete structured export on demand. Your data is readable without us.
Google Cloud, MumbaiData resident in IndiaEncrypted in transit and at restField-level permissionsImmutable audit logSSO · SAMLFull export on demand
Implementation

Institutions go live in three weeks. Students in three minutes.

SchoolDeck, CampusHub and TutorDesk are configured with you: the year first, people second, money once the ledger reconciles. ExamEdge needs no rollout — a student signs up on a phone and starts with a diagnostic.

  1. Week 1Shape the yearBranches or centres, academic year or batch calendar, fee heads, grading or test pattern. We sit with the office, not IT.
  2. Week 2People and balancesStudents or enrolments, staff or faculty, opening balances, previous marks. Files validated before anything goes live.
  3. Week 3Three desksThe front desk, accounts, and whoever teaches. Everyone else learns from them.
  4. Go liveAttendance first, money nextAttendance or follow-ups first; fees switch at the next month boundary so the books close cleanly.
Things we don’t do

Six rules, written down.

Most of what makes institutional software bad is a business decision, not a technical one. These are ours.

No ads
Not in the parent app, not in the student app, not in a “free tier” later.
No lead resale
Enquiry data in TutorDesk is yours. We do not see it as a market.
No content library
We are the record, not the syllabus.
No releases during exams
A named engineer stays on standby instead.
No shared student records
A school, a college, a centre and a student are four customers. Their data never meets.
No lock-in
Your data is readable without us. Export is a button, not a phone call.