انتقل إلى المحتوى الرئيسي

هذه الصفحة غير متوفرة بالعربية بعد. أنت تقرأ النسخة الإنجليزية الأصلية. ترجمة الواجهة العربية قيد المراجعة.

Technology services · since 2011

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.

15+ years
of building, since 2011
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

Since 2011, 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, since 2011

PrajnaBytes grew out of years of hands-on work: building, teaching and keeping systems running. That persistence is still how we work today.

Read our story
  1. 2011

    The work begins as ISCL Online

    A practice in New Delhi takes on web development and digital marketing work for organisations in Delhi.

  2. Training

    Sharing what we learned

    Under the ISCL Online name, we deliver technology training to students of University of Delhi colleges.

  3. 2023

    PrajnaBytes is incorporated

    PrajnaBytes International Private Limited is incorporated, carrying forward the work and client relationships of ISCL Online.

  4. Today

    Building and operating systems

    Six service areas, from business software and AI automation to running the systems clients rely on every day.

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

دراسة حالةبحث مستقلقراءة في 17 دقيقة

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

رؤية تقنيةتنفيذ داخليقراءة في 4 دقيقة

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

رؤية تقنيةتنفيذ داخليقراءة في 4 دقيقة

A readable XML sitemap without XSLT, before Chrome removes it

Chrome removes XSLT from stable releases in version 158 (17 November 2026), and with it the usual way of making an XML sitemap readable in a browser. CSS on XML is not being removed. This is how our sitemap uses a plain CSS stylesheet instead, and what that approach cannot do.

  • XML sitemaps
  • Search engine optimisation
  • Web standards

هل لديك ما تريد بناءه أو إصلاحه أو رعايته؟

أخبرنا عنه في بضعة أسطر. نقرأ كل استفسار ونرد بالأسئلة المهمة.