Custom software · AI · Automation · Noida, India · IST (UTC+5:30)
Custom software and AI systems built around your business.
We build internal tools, customer platforms, AI integrations and automations that reduce manual work. You own the code, the infrastructure and the accounts.
What we build.Around how your business actually works.
Every business has different workflows, data, teams and customers. We build the software around yours, so it fits the way your team already works.
01 · Custom software
Software your team relies on every day
Their customers use it too, from the other side of the same system.
Internal business software
One system for your team, in place of scattered spreadsheets and apps.
Admin dashboards, with permissions set per role and per record
Reporting, exports and PDF generation
Payment, KYC, WhatsApp and Telegram integrations
Several brands or publications on one system, from day one
Customer platforms and products
Complete products your customers use, from the database to the interface.
Public sites on the same API and database as your team’s tools
AI features built in, with a check around every output
Deployed to your own accounts, with a documented API
Handed over with a walkthrough, and support whenever you want it
02 · AI integration
Uncertain results go to a person for review.
AI built into the work your team already does
Checked, tracked and part of a real workflow.
Voice agents and outbound calling
Automated phone calls, with every result captured as structured data.
Outbound calls placed and tracked, call by call
What the caller wants captured as structured data, with a confidence score
Signed provider webhooks, verified and handled once even if sent twice
Anything the model is unsure about goes to a person
Document, PDF and image extraction
Documents, scans and PDFs turned into records your team can search and use.
Printed and scanned documents read into validated records
Images checked before they are used
Scheduled processing, with retries and a review queue
Every output verified before it is saved or published
03 · Automation and engineering
Engineering support for growing teams
Automation that keeps work moving
Less manual work, and systems that keep up as you grow. Repetitive work automated, your tools connected, and senior engineering on your codebase when you need it.
IntegrationsPayments, KYC, WhatsApp, Telegram and signed webhooks, wired into your system
Scheduled workDocuments and data processed on a schedule, with retries and a review queue
Architecture reviewsReviews and database work for a system that has outgrown its design
Your repositoryCommits in your repository from week one, on code and accounts you own
IllustrationIST (UTC+5:30)
02 / Capabilities
Technologies we work with.
Each one earned its place by holding up on a real project.
AI and automation
OpenAI
Anthropic Claude
Vision extraction
Voice agents
Vapi
Deepgram
Output verification
Backend
Node.js
NestJS
TypeScript
Express
Fastify
REST
Jest
Data
PostgreSQL
MongoDB
Drizzle
Mongoose
Redis
BullMQ
Frontend
Next.js
React
TypeScript
Tailwind CSS
Recharts
Infrastructure
AWS
S3
SES
Docker
CI/CD
Vercel
Practice
Schema design
RBAC
Webhooks
Audit logging
Swagger/OpenAPI
03 / Case study
One client, a whole publishing platform.One API, one database, and the three surfaces that sit on top of it.
OG Media 360 — A distribution-first media company
75 days
From first commit to handover
4
Products delivered: one API, three front-ends
9
Business functions in one system, from leads to invoices
The problem
A media company running its commercial side on spreadsheets and its publishing on WordPress. Leads, clients, proposals and invoices lived in different places from the articles, and nobody could see the whole business at once.
What we built
We built the platform underneath all of it: one API, one database, and the surfaces that sit on top — a workspace for staff, the public network site, and a reader front-end for one of its titles. Each new publication is a tenant on the same system rather than another site to maintain.
Access control
“Row-level scope answers 404 rather than 403, so one employee cannot confirm another’s lead exists.”
To anyone without access, a colleague’s lead or client looks exactly like one that was never created, so each pipeline is seen only by the people meant to see it.
404, not 403
OG Media 360 · Staff dashboard
Detail
A rich-text editor with a media library, and bulk article import driven from a Google Sheet
AI-drafted proposals with a live branded preview, exported to PDF through headless Chrome
An owner-configurable permission matrix on top of fixed staff ranks, so access is set without a deploy
Money kept as exact decimals, and revenue read only from invoices actually marked paid
Posts go live on their publish date, read from the record itself rather than a scheduled job
Stack
NestJS
Fastify
PostgreSQL
Drizzle
Next.js
TypeScript
AWS S3
04 / The work
Two platforms on one architecture.Both built for clients, from the database up.
Built for real operations. Every screen on this page is a capture of the software itself, running, with names and some figures replaced for privacy.
Physical tickets move from an operator down through distributors to sellers, and money moves back up the same chain. Each distributor sees only its own branch: its sellers, stock and sales. A sender can only pass on stock it holds, and uploads are all-or-none — one bad ticket number rolls the batch back and reports which were missing.
Scope
Backend architecture and build, and the distribution admin since 2026
₹8.0 Cr in prizes distributed across 25,742 winners
2.1M QR tickets issued, every movement checked against an immutable ledger
Printed result sheets read by a vision model, matched across 5 prize tiers
Booking over WhatsApp and Telegram as a conversation state machine
The public network site — the third surface on the same API as the workspace.
OG Media 360 · ogmedia360.com
Also built
StartupByDOC
A second publication on the same API, built and awaiting its launch.
StartupByDOC
05 / Accountability
Built with accountability from day one.
We started Ovast to build software end to end, and to stay accountable for every decision in the scope we agree with you.
We do the architecture and write the code ourselves, which is why the scope we agree to is a scope we can actually hold. When a build needs specialist help, the written scope names it before you commit.
Automation does the repetition. What ships is still a decision someone makes, and on your project that decision is ours to answer for. You own the code, the accounts and the documentation, so everything we build stays yours to run.
Dhananjay SinghFounder
Based in
Noida, India
Working hours
IST (UTC+5:30)Overlapping Europe, the Middle East and the US east coast.
Clear scope. Direct communication. Working software early. The price and the date are fixed in writing before the build begins.
01
Understand the problem
Thirty minutes on your business, your workflow, your users and what is currently in the way.
Thirty minutes
02
Write the scope
What we will build, what is included, what is out of scope, and a fixed price with a date — in writing, before any money moves.
Fixed price, fixed date
03
Build and show progress
Work lands in your repository from the first week. You see the product early, while changes are still easy and affordable.
Commits from week one
04
Handover and support
The code, a documented API, deployment notes and a walkthrough. You own the code and the accounts it runs on. Support after launch is there whenever you want it.
You own the code
07 / Questions
Before you ask.The questions that come up on nearly every first call.
Another question?
Ask it directly. A call reaches the people who would write the code, and the assistant answers from what is published here.
The people who design the system also build it. You work directly with the people making the technical decisions, from the first call to the handover.
What kind of projects do you take on?
Custom software, internal platforms, customer-facing products, AI integrations, workflow automation, APIs, and improvements to systems you already run.
Can you add AI to our current software?
Yes. We add practical AI features to an existing product or workflow — document and PDF extraction, image checks, voice agents and content pipelines — built into the software your team already uses.
How do you make AI reliable?
We add validation, confidence scores, review queues and retries, matched to the risk of the task. Important outputs are checked before they are saved or published, and anything uncertain goes to a person.
How do you charge?
Fixed price against a written scope for defined builds, so the number you agree is the number you pay. Monthly retainers for ongoing work, and a day rate for architecture reviews. Pricing comes after the first call, once the work is actually understood.
How long does a build take?
An integration or a contained AI feature is usually two to four weeks. A full product build with its own schema, API and interface is typically six to twelve weeks. You get a date in the written scope, before you commit.
Can you work on a codebase we already have?
Yes, and a good share of the work is exactly that — a system that has outgrown its original design, a database that has become slow, or an AI feature that works in a demo and falls over with real users. An architecture review is often the cheapest place to start.
How do we work together day to day?
Commits to your repository from week one, a written update each week, and a call whenever you want one. We work from India on IST, with working hours that overlap Europe, the Middle East and the US east coast.
Who owns the code?
You do, from the first commit. The code lives in your repository, deployments run in your accounts, and the credentials are yours. You get the documentation and access needed to run it.
08 / Contact
Tell us what you are building.A short call is usually enough.
It is enough to know whether we are the right fit. If we are not, we will say so and point you somewhere better.
