San Antonio, Texas
We audit and build websites, software, and AWS cloud solutions.
Five things, and they connect.
From a one-page site to the infrastructure under an application.
01 / Website audits
Find what your website is losing
Every page measured, every link and form checked. A written list of what is broken, and the price to fix it.
02 / Website design & build
Build the website itself
Menu or catalogue, hours, directions, financing a customer can start on the page, and a store running off the register you already use. Your domain. Your files.
03 / Software & payments
Software, not just pages
Card payments, customer accounts, stock that cannot sell the same item twice, and an AI agent where it earns its place. Built, deployed, kept running.
04 / AWS cloud architecture
Architecture on AWS
How it deploys, what it costs to run, what happens when it grows. The engineering the rest sits on.
05 / Search & local listings
Getting found is its own job
Google Business Profile on your own account, Search Console verified, every page declared to search engines. With a written record of what was done.
Audits
A speed score measures how fast a page paints. It says nothing about whether the page works — a link that goes nowhere, a form that posts to nothing, an enquiry handed to a mail program that records no lead. We measure both.
What the report says
Timings are written as what a visitor experiences, not as metric names. The home page of an Islamic center we audited:
5.4 sSomething appears
12.4 sPage mostly filled in
16.8 sButtons work
Performance
Does the page arrive, and how long is the wait?
8 of 105 loads never finished. A blank page, leaving no record it happened.
3.7 s on their server before the site could start. Half a second is the mark.
A background video, 2,377 KB — 43% of the page. The content waits behind it.
Anti-spam code on all seven pages, 401 KB a visit, guarding a form that had its own.
Accessibility
Can a blind visitor use it?
Links with no name on every page, the logo included. No way back to the home page.
“Skip to content” pointed nowhere. The one control built for blind visitors.
The contact form sat in an unlabelled window. Never announced.
9 event posters with no description. The name and date are inside the image.
Best Practices
What does the browser itself object to?
A donation button with no link behind it. Pressing it did nothing.
3 of 15 loads arrived with no design files. Plain text on white.
Five security protections off, including the one against another site framing the donation page.
A payment company setting cookies on all seven pages, including where nobody pays.
Search
Can it be found, and is what is found right?
Google could not fetch the home page. A page it cannot fetch stops being trusted.
Opening hours nowhere a machine can read. 7 of the 10 local results show them.
Every page titled the same abbreviation. Google’s listing used the full name.
9 events search could not reach — the only part of the site that changes.
Sites
Built and delivered
Concepts
They do not look like each other
Each one drawn from that business's own references — its colours, its room, its menu. Every one below is a concept.
Products
Where a website stops being enough.
Mahall
In private beta
An app for Muslims moving to a new city. You enter the city, the addresses you are choosing between, and where you would commute to. It returns one assessment: mosques, halal restaurants, halal groceries and butchers, and travel time to each on foot, by transit, by bicycle and by car. Prayer times at both solstices tell you how long a fasting day runs there in Ramadan.
TypeScript on Node, an Anthropic model driving five MCP tools over Google Places, Google Routes and a prayer-times API. DynamoDB, AWS. 811 tests.
Terres Vertes
Live
A ticketing and payments platform. Someone buys a ticket, the money moves, and a signed ticket with a QR code arrives in their inbox — without a person in the middle at any point.
We built the backend, the payment service and everything after the payment. Stripe checkout with optimistic concurrency control on DynamoDB, so the same seat cannot sell twice when two people press buy at once. Fulfilment on SQS, issuing KMS-signed tickets and generating the PDF. 660+ tests.
The front end is not the finished article yet. That is the next few months of work. What sits behind it is built.
Cloud
Two production systems on AWS.
Mahall and Terres Vertes are both deployed. Architecture, infrastructure, security and CI/CD on each — not a piece of one, all of it.
Stripe checkout with optimistic concurrency control on DynamoDB, so the same seat cannot sell twice under load, and compensating transactions when a write half-succeeds. Fulfilment on SQS issuing KMS-signed tickets. Sessions bound to a non-extractable browser key, so a stolen token is inert without it. Deployments that roll themselves back on a CloudWatch alarm with nobody watching. 1,400+ tests across the two.
Also on npm: a Pino transport for CloudWatch with bounded backpressure, a circuit breaker, and an awaited flush on shutdown so the last logs before a crash are not the ones you lose. It takes no credentials — nothing static to leak into a config.
npm i @chisme/pino-cloudwatch
That is the same reasoning behind the websites: static files on a CDN, on an account the client owns, with nothing rented from us.
Tell us the business and what is not working.
If a website is not the answer, we will say so.
Conakry Technologies LLC · San Antonio, Texas
Also building mahall.app.