Skip to content

Services

We build the software your operation runs on

From a company website to a platform a whole office depends on. One team across the stack: design, build, hosting and the years after launch.

What KAEL builds

  • 01

    Websites

    Company, campaign and organization sites that load fast on any phone and pass an accessibility check before they go live.

    • Day and night themes
    • Search-ready from the first day
    • Forms that reach your inbox
    Ask about websites
  • 02

    Portals and web apps

    For the people you serve and the team that serves them: sign-in, records, requests and payments, each action on record.

    • Roles and permissions
    • Audit trail
    • Works on a weak signal
    Ask about portals and web apps
  • 03

    Mobile apps

    iPhone and Android from one codebase, published to both stores and tested on real devices before every release.

    • App Store and Google Play
    • Notifications
    • In-app account deletion
    Ask about mobile apps
  • 04

    Government systems

    For barangays, municipalities, provinces and offices in Congress and the Senate, built around RA 10173 and the way an office actually works.

    • Filipino and English
    • Data kept per office
    • Exportable for COA, NPC and DILG
    Ask about government systems
  • 05

    AI inside your system

    An assistant where it saves time: finding, drafting and sorting. Never required to finish a task, and never sent more data than it needs.

    • Answers checked before they act
    • Spending caps
    • Still works when AI is down
    Ask about ai inside your system
  • 06

    Migration and managed operations

    Move what you already have without your visitors noticing, then keep it monitored, backed up and up to date.

    • Copied and tested before the switch
    • Backups that are restored to prove them
    • A log of every change
    Ask about migration and managed operations

AI inside your system

AI that works for your people, with guardrails

  • Assistants in your system

    Answers questions from your own records and help pages, in English and Filipino, inside the screens people already use.

    Answers only from your data, and says when it does not know

  • Document drafting

    First drafts of letters, certificates, reports and replies, ready for a person to check, change and sign.

    A person signs; the AI never sends on its own

  • Search that understands

    Find a record by what someone means, not only the exact words they typed, across names, notes and files.

    Respects every role: nobody finds what they may not open

  • Sorting and routing

    New requests, messages and tickets read, labelled and sent to the right person or queue as they arrive.

    Every decision logged and easy to overrule

  • Agents that run your cloud

    Your own AI coding agent can deploy, read logs and roll back on KAEL Cloud, through the open MCP standard.

    Only on the projects you allow, with every action recorded

  • AI with guardrails

    Text from users never steers it, personal data stays out of prompts, and a daily spending cap and an off switch come built in.

    The system keeps working when the AI is down

How a project runs

Six steps, in the open

  1. 01

    Discover

    We start with what needs to exist, who will use it and what it must never do.

  2. 02

    Plan

    A written plan: what gets built, in what order, what it costs and what done looks like. Nothing starts until you agree to it.

  3. 03

    Build

    Kael builds it in small pieces you can see, each piece tested as it is written.

  4. 04

    Prove

    Before anything goes live it passes the gates: tests, a real browser at every screen size, accessibility, security and speed.

  5. 05

    Approve

    A person at KAEL approves every production release. Our tooling refuses to release without that approval.

  6. 06

    Run

    If you want us to keep it running: monitoring, backups, updates and fixes, with a log of every change.

What you get

Every project comes with these

  • A written plan first

    What gets built, in what order, what each part costs and what done looks like. Nothing starts until you agree to it.

  • Work you can see

    Small pieces you can open and try as they are built, not one big reveal at the end.

  • Proof before release

    Every release passes the same gates as this site: tests, every screen size, accessibility, security and speed.

  • A person's approval

    A person at KAEL approves every production release. The tooling refuses to release without it.

  • Documents you can use

    Help for your people in plain words, and the records an auditor or the NPC can ask for.

  • Care after launch

    If you want it: monitoring, backups that are restored to prove them, updates and fixes, with a log of every change.

Tell us what needs to exist

The reply says whether Kael or a person at KAEL wrote it.