Build your ideas

HaveStack builds, integrates and maintains the systems institutions depend on. Enterprise software from Dhaka.

Mandate

How HaveStack takes on work.

Four conditions apply before an engagement opens.

Business first

Open to any organisation. Business and institutional engagements take priority.

Systems, not brochure sites

Operational software that holds records and enforces workflow.

A named owner

One person on the client side approves scope and signs acceptance.

A defined budget

Cost follows scope and is agreed in writing. No price list is published.

HaveStack works with anyone who needs a system built properly. Business to business engagements are scheduled first, because they arrive with a named owner, a defined scope and a budget, which is what lets the practice commit to a delivery date.

What the practice builds.

Five practice areas, each carried from specification to live service.

Enterprise resource planning

One authoritative record of finance, procurement, inventory and payroll, with approval chains enforced in software.

General ledgerProcurementInventoryPayroll

Systems under management.

A system does not end at launch. HaveStack keeps the parts that fail quietly in good order.

Maintenance is available on systems HaveStack built and, after a written technical review, on systems it did not.

Request a meeting

AI and language models

  • Model versions pinned, upgrades tested before they land
  • Prompt and output checked against a fixed evaluation set
  • Token spend tracked with a monthly ceiling
  • Fallback routing when a provider degrades
  • Retrieval sources re indexed on a schedule
Learn more about AI and language models

Databases

  • Backups taken on schedule and restored in a drill
  • Slow queries traced, indexes rebuilt
  • Migrations applied with a written rollback
  • Replication and failover verified
  • Growth watched before storage runs out
Learn more about Databases

Backend and infrastructure

  • Dependencies patched, advisories reviewed weekly
  • Certificates and domains renewed ahead of expiry
  • Uptime and error rates alerted to a named contact
  • Capacity reviewed against measured load
  • Logs retained for the period the contract sets
Learn more about Backend and infrastructure

Response and reporting

  • Response times set in the service agreement
  • Incidents written up with cause and correction
  • Releases scheduled, never applied unannounced
  • A monthly report the client can file
  • Access reviewed each quarter
Learn more about Response and reporting
Products

Software we run ourselves.

Products built and operated in house, on the same standards as client work.

Resource planning suite

Ledger, procurement and stores for mid sized institutions.

Not yet public

Learning platform

Course delivery, assessment and transcripts for training bodies.

Not yet public

Service intake portal

Application intake and case tracking for public counters.

Not yet public

Interface layer

Moves records between systems under a fixed contract.

Not yet public

Operations console

Monitoring, release and recovery for systems under management.

Not yet public

Organisations we build for.

Named with their agreement. Further references are available under a non disclosure agreement.

  • Gungchil

Official partners.

Organisations and institutions that work alongside the practice.

  • Avane Labs
  • ARIES
  • Amaze Youth Chess Tournament
  • First Principles
  • The Outliers Club

Where these systems run.

Six sectors where a failure is expensive.

Government and public administration

Registries, service delivery and internal administration.

Banking and NBFI

Origination, servicing and regulatory reporting.

Education

Admissions and academic records.

Healthcare

Patient administration under access control.

Real estate and construction

Cost control and handover records.

Development and NGO

Programme monitoring and donor reporting.

Delivery

How an engagement runs.

Five stages, each closing on a written output.

Discovery

The practice records how the organisation operates today.

OutputScope document

Architecture

Data model, integrations and hosting fixed before any code.

OutputTechnical specification

Build

Delivery in reviewable increments against agreed scope.

OutputAccepted release

Handover

Source, credentials and documentation transfer to the client.

OutputOperations manual

Operations

Monitored and maintained under a service agreement.

OutputService report

What HaveStack commits to in writing.

Twelve commitments, written into every engagement contract.

Delivery and documentation

  • Written scope before any code
  • Client read access to the repository
  • One configuration across development, staging and production
  • Each stage accepted against the written specification

Security and access

  • Least privilege on every account and integration
  • Encryption in transit and at rest
  • Audit trail on every record change
  • Access withdrawn the working day someone leaves

Ownership and continuity

  • Intellectual property transfers on final payment
  • Hosting, domains and repositories in the client name
  • Established open technology, documented for another team
  • A notice period and a defined exit process

Governance and standing.

Corporate standing

HaveStack is an enterprise software practice working in partnership with Amaze Consortium and with ARIES, its research and exploration society.

Those relationships give an institutional buyer more than one organisation to examine, and continuity that does not rest on any one individual.

Related organisations

HaveStack TechnologiesSoftware practice
Amaze ConsortiumParent
ARIESPartner, research and exploration society
Practice
Independent
Partners
Amaze, ARIES
Base
Dhaka, Bangladesh
Field
Enterprise software
Engagement

Start with a meeting.

A first meeting runs about forty minutes. It establishes what the organisation needs and whether HaveStack is the right practice for it. Cost is discussed once the scope is understood.

  1. Submit the brief
  2. Reply within two working days
  3. Meeting scheduled
Request a meeting