Skip to main content

Technology services · incorporated 2023

We build the systems organisations run on, and we stay to keep them running.

Software, automation, digital services and the infrastructure underneath them, designed with care and looked after long after launch.

Incorporated 2023
in Uttar Pradesh, under the Companies Act, 2013
6 service areas
from software to operations
Government, education, industry
and non-profit organisations served
Your code, your data
handed over and documented

What we do

Six ways we help organisations work better

Each service is defined by the problem it solves, what it includes, how it is delivered and how it is supported afterwards.

Clients

Organisations we have worked with

We have worked with organisations in government, education, the non-profit sector and industry.

  • Government
  • Education
  • Non-profit
  • Industry
  • GovernmentGovernment of NCT of Delhi
  • University of Delhi logo
  • Delhi Skill and Entrepreneurship University logo
  • PGDAV College (Evening) logo
  • Chowgule Public School logo
  • BMVB ASMA New Delhi logo
  • Blue Pen NGO logo
  • Pasupati Acrylon Ltd. logo

Our journey

Learning by building

PrajnaBytes is a startup growing in clear stages, from idea to a scaled business. Today we are at MVP and market launch.

  1. Stage 1

    Ideating

    Identifying real problems organisations face and shaping ideas to solve them.

  2. Stage 2

    Prototyping

    Turning ideas into working prototypes and trying them early with users.

  3. Stage 3

    Testing & Validation

    Testing with real users and validating that the solutions meet real needs.

  4. Stage 4

    We are here

    MVP & Market Launch

    Our services and first products are live and in use by our early clients.

  5. Stage 5

    Scaling & Growth

    Next: growing our team, our client base and our products.

  6. Stage 6

    Maturity & Expansion

    Later: a stable, established company expanding into new markets.

How we work

Clear from the first conversation to years of support

  1. Understand

    We study the current process or system, the people who use it and the outcome that matters.

  2. Agree in writing

    Scope, responsibilities, acceptance criteria and support terms are written down before work begins.

  3. Deliver in stages

    Working results are reviewed with you as we go, so problems surface early, not at handover.

  4. Operate and improve

    Where agreed, we keep the system maintained, monitored and improving, and report on it.

What you can count on

Responsible for the service, not only the delivery

Clients should stay because the work keeps being useful, never because their systems are locked away.

Your systems stay yours
Source code, credentials and documentation are handed over and kept current.
Defined scope
Every engagement states what is included, what is not, and how changes are handled.
Measured service
Continuing services are reported against agreed targets, with work and incidents recorded.
Technology chosen for the problem
Tools, including AI, are used where they improve outcomes or costs, not for their own sake.

Research & Case Studies

What we have investigated and learned

Written from evidence you can check, with the limits stated.

All research and case studies

Case studyIndependent research16 min read

AIIMS Delhi Website Ad Injection: A Historical Third-Party JavaScript Case Study

In December 2022 a visitor-counter script on the official AIIMS Delhi website was found to be placing third-party advertising at the top of the page. This case study reconstructs what happened from the original report and from archived copies of the script, separates verified facts from interpretation, and sets out what the episode teaches about third-party JavaScript.

  • Third-party JavaScript
  • Web security
  • Supply-chain risk
  • Content Security Policy

Case studyInternal implementation13 min read

Overcoming E-Filing Scrutiny: The Bulk Field Signer Solution

E-filing before the Allahabad High Court needs a visible signature on every page. Signing page by page took hours; an early build of Bulk Field Signer signed a 184-page petition in 30 to 45 minutes, and it passed scrutiny without objection. Version 2.0, now free and open source, puts a stamp on every page and secures the whole file in one signing step.

  • E-filing
  • Digital signatures
  • Document signing
  • Open source

Technical insightInternal implementation4 min read

A strict Content Security Policy for a React website, without inline styles

How the PrajnaBytes website runs a Content Security Policy with no 'unsafe-inline' for scripts or styles, while still using React, UI libraries and dynamic effects: stylesheet classes, one per-request nonce, CSS custom properties set through the CSSOM, and self-hosted assets.

  • Content Security Policy
  • Web security
  • React

Have something to build, fix or look after?

Tell us about it in a few lines. We read every enquiry and reply with the questions that matter.