Talk to us

Three addresses, one repository and a calendar link. The table below sets out what to send where and what comes back, with response times we actually hit rather than the ones a support policy would like to advertise.

Last reviewed 2026-10-15

Enquiry routes and the information to agree before sharing data
If you are asking aboutRouteResponse expectationUseful first information
Pilot or evaluation enquiryRossConfirm with RossApproximate enrolment, current system and the workflow to improve. Do not send family records.
Pricing questionRossConfirm with RossPublished rate, cohort size, channels, countries and written quote assumptions.
Security review, DPA or vendor questionnaireAsk Ross for the verified review routeAgree scope and timingQuestionnaire and required evidence. Approved agreement versions and vendor facts need review.
Migration or importer questionGitHub issues for synthetic cases, or Ross for a permitted private sample routeAgree scope and timingSource product/version and export schema. Keep family records and secrets out of public issues.
Vulnerability disclosureAsk Ross for the verified security reporting routeConfirm monitored intake and expectationsReproduction steps without student records or secrets; agree a secure route for sensitive details.
Press or analystRossConfirm with RossQuestions, scope and requested timing; no customer or certification claim is inferred.
Customer supportUse the authorized route recorded during school onboardingAgreed school hours, escalation and coverCase reference and redacted symptoms. Coverage and response terms must be confirmed before launch.

The addresses, and what each one is for

ross@getkastr.com is the founder and the default. Product enquiries, pricing questions, press, and anything you are not sure how to route. It is also the escalation path if another address has gone quiet, and there is nothing above it.

Ask Ross for the verified security review and reporting routes. Agree questionnaire scope, evidence, document versions and timing before relying on a response expectation. Keep student records and secrets out of initial enquiries.

School onboarding must record the authorized support route, monitored hours, response expectations, escalation owner and absence cover. These operational arrangements require confirmation with Ross before launch; this page does not establish staffed coverage.

GitHub is at github.com/kastr, where the ParentSquare importer, the CLI and the MCP server live under MIT licences. Importer bugs are best raised as issues; they are public, which is the point.

A calendar is at cal.com/kastr/intro for a 30-minute slot if you would rather pick a time than exchange emails. What that half hour covers is set out on the product conversation page, so nobody arrives expecting a slide deck.

What to include so the first reply is useful

The difference between a one-line reply and a useful one is usually four facts, so if you have them to hand, include them:

  • District and approximate enrolment. Enrolment sets the pricing band and changes which parts of the answer matter.
  • Current vendor and renewal month. This is the single most useful thing you can tell us, because it determines whether a summer cutover is even available to you this cycle or whether you need a bridging extension first.
  • What is actually broken. A price increase, a reach problem, a front-office workflow, an acquisition you are unhappy about. The answer differs sharply, and for a couple of those the honest answer is that another vendor fits better.
  • Your hard requirements. If a completed SOC 2 report, SSO, attachments or push notifications are non-negotiable, say so in the first email and we will tell you in the first reply that we do not have them, rather than discovering it together in week six.

You do not need to email us to get the commercially sensitive things. The price list is published. The current engineering posture, processing-path inventory and retention gaps are published. The comparison pages carry the rows where we lose. Email gets you the contract documents and a human; it is not the gate on the information, because there is not one.

What we will not do

We will not put you into a nurture sequence. One reply from a person, then a follow-up if you asked for one, and silence otherwise.

We will not require an NDA before showing you the master agreement or the DPA. A contract you cannot read before signing is a negotiation you have already lost, and legal review is exactly the stage where we would rather be slow and open.

We will not quote you a price different from the published one. The proposed price terms are a 36-month rate lock followed by annual increases capped at the lesser of CPI-U or 5%; confirm the current written quote and agreement with Ross.

We will not claim a capability we do not have in order to stay in an evaluation. If you ask about SSO, file attachments, push notifications, native SIS connectors or a completed SOC 2 report, the answer today is no in each case, and it will be no in the email as well as on the trust page.

Where we are, and when we answer

Confirm response hours, timezone, escalation and absence cover with Ross. No continuous monitoring or fixed reply time is established by this page.

Ask Ross for the verified security reporting route, monitored intake and response expectation. Do not include student records or secrets in an initial report. Secure handling and disclosure coordination require agreement with the responsible owner and reporter; no fixed acknowledgement time or funded bounty programme is established here.

If an enquiry needs follow-up, contact Ross with the case reference and agreed expectation. Do not include family records or secrets; this page does not establish a same-day response.

Questions people actually ask

How quickly does Kastr respond?

Agree response expectations, hours, timezone and scope with Ross. A school support arrangement also needs an authorized route, escalation owner and absence cover; no fixed reply time is established here.

Who do we contact for a security review or a DPA?

Ask Ross for the verified security review route and current reviewable documents. Agree scope and timing; do not include student records or secrets in an initial enquiry.

Where do we report a security vulnerability?

Ask Ross for the verified security reporting route and response expectation. Do not include student records or secrets; agree secure handling and disclosure coordination with the responsible owner.

Do we have to talk to sales to get a price?

No. The full price list is on the pricing page: $3.50 per student per year under 5,000 students, $3.25 to 14,999, $3.00 above that, one tier with everything included. Emailing us gets you contract documents and a human, not a number you could not otherwise see.

Can we speak to an existing district using Kastr?

Reference availability depends on timing and permission from each school. Email us with the school size and use case you need to validate and we will tell you directly what is available.

Published pricing. Current capabilities included.

$3.50 per student per year under 5,000 students. No tiers or add-on modules. Normal messaging is included under a published fair-use allowance, with transparent cost recovery only above it.