Start a project

/00 Software company

Software built to last.

Aeon builds software for businesses whose work does not fit generic tools, and keeps it running.

Scroll to explore

An aeon is an age.We build software to last one,through new owners, heavier traffic, and every engineer who opens the code after us.

/02 How we work

How work moves from idea to production.

Four phases. Each one ends with a document you can read and a decision you can make.

Phase 01

Discover

We study the code, the data, and the constraints before we commit to a plan.

You receive

A written report with risks, options, and a cost range.

Phase 02

Define

We record the scope, the milestones, and the definition of done in one signed document.

You receive

One signed document with the scope, the milestone plan, and the acceptance tests.

Phase 03

Deliver

We release small, tested pieces. You review working software every week.

You receive

A live demo each Thursday, a status report and release notes each Friday, and code you can inspect.

Phase 04

Sustain

We stay accountable after launch. We monitor, patch, and document the system.

You receive

Runbooks, architecture notes, dashboards, and a handover you can audit.

/03 Ways to work with us

Pick the software that fits how you work.

  • 01

    Industry-specific software

    Software made for one kind of business, built around the rules and daily work of your industry.

    FitBest when your work follows the rules of one industry, not a generic template.

  • 02

    Custom software

    A fixed-scope build by one senior team. It ends in software you own, or in a product.

    FitBest for a new platform, a portal, or a scoped modernization.

  • 03

    Ongoing ownership

    A monthly software subscription that includes upkeep, patches, monitoring, and small improvements.

    FitBest for business-critical systems that must not stop.

/04 Principles

The rules behind everything we build.

  1. 01

    Decisions on paper

    Every decision, estimate, and change has a document you can read.

  2. 02

    Tests before release

    Nothing reaches production without automated tests and a human review.

  3. 03

    Made for the next team

    Any competent team can continue our work with the documentation we leave.

  4. 04

    Ranges, not guesses

    We give each estimate as a range, name what drives it, and update it when facts change.

  5. 05

    Least access, always

    Each person gets only the access the work needs. We encrypt data and audit dependencies on every build.

  6. 06

    Steady in incidents

    Every incident follows a runbook and gets a timeline and a blameless review.

Measure us against them.

/05 Alongside your team

Our engineers work alongside your team, on site when the work needs it.

  • 01Weekly demosYou see working software every week, not a slide.
  • 02Written statusA short written report each week. Progress, risks, decisions.
  • 03Direct access to engineersYou can talk to the engineers who write the code. Questions do not wait in a queue.
  • 04One trackerOne backlog, in your tool or ours. We record every task and decision there, not in chat.
  • 05On site when neededWe come to your site when the work needs it: workshops, launches, and hard problems.
Example of shared working time in one dayThree work schedules on one 24-hour axis. A band marks the time set aside for demos and reviews.Your teamAeon · AAeon · B00:0006:0012:0018:0024:00Demos and reviewsOne day
Example only. We agree the schedule with you before work starts.

/06 Next step

Start with the problem.