Demo mode. Sample data only.
Keisan

Status

The parts of Keisan, and how to report a problem.

A map of the service, so a report can say exactly where something broke. If something is not working, tell us the page, the account and the time.

Last updated · October 23, 2026

Report a problemSecurity overview

Components

5

Web, estimation, sign-in, storage, approvals

Report a problem

Email

admin@jishulabs.com or the contact page

Vulnerabilities

Disclosure

Reported through the disclosure policy

Systems

Service components

Each part is listed on its own so a report can say whether a problem sits in sign-in, data, estimation or the pages themselves.

Web

Web application

The public site, the dashboard and the signed-in pages.

Routes

  • /
  • /dashboard
  • /projects

Estimation

Estimation

Turning a brief into line items, and the estimate and proposal pages.

Routes

  • /calculate
  • /estimates
  • /api/estimates

Auth

Sign-in

Sign in, sign up, email confirmation and the demo workspace.

Routes

  • /auth/signin
  • /auth/signup
  • /auth/callback

Storage

Data storage

Projects, estimates, rate cards, settings and exports.

Routes

  • /rate-cards
  • /settings
  • /api/settings

Clients

Client approvals

The read-only proposal a client opens from an approval link.

Routes

  • /approve/…

Reporting

What to put in a report

Four details let us find the problem quickly without asking you twice.

  1. 01Where

    The address of the page, and which of the parts above it belongs to.

  2. 02Who

    The email you were signed in with, or that you were using the demo.

  3. 03When

    Roughly when it happened, with your time zone, and whether it keeps happening.

  4. 04What

    What you expected to see and what you saw instead. A screenshot helps.

Contact

Report a problem

Support

Send us the details

Email admin@jishulabs.com or use the contact page. For a security weakness, follow the vulnerability disclosure policy instead.