How we manage internal tools.
xAppHub is a central portal for every app BuildPad builds for you. Employees open their assigned apps from one place, and admins manage access, updates, and lifecycle for all of them from a single portal.
First, the name
xAppHub
YourCompanyAppHub
The x is your name. The screens here use YourCompanyAppHub, standing in for whatever yours would be.
Your whole organization signs in here, so it carries your name rather than ours.
A central portal for everyone.
The xAppHub portal is where everyone in your organization signs in. Each person sees only the applications they are entitled to. It is the part most people use.
Good morning, Priya.
- Expense ClaimsFinance
- Purchase ApprovalsFinance
- Vendor MasterFinance
- Budget TransfersFinance
- Month-End CloseFinance
- Leave & AbsencePeople
- PayslipsPeople
- IT Service DeskTechnology
Good morning, Daniel.
- Shift RosterOperations
- Leave & AbsencePeople
- PayslipsPeople
- IT Service DeskTechnology
One list of every application.
xAppHub lists every application built in your company in one directory. An application joins the list the day BuildPad creates it.
Applications
34 applications across four business units
| Application | Owner | Business unit | Users | Environment |
|---|---|---|---|---|
| Expense Claims | Finance | Group | 1,840 | Production |
| Leave & Absence | People | Group | 4,210 | Production |
| Contract Register | Legal | Group | 67 | Staging |
| Incident Reports | Operations | Singapore | 289 | Pilot |
Owner, business unit, users, environment. 34 applications here, and the thirty-fifth costs the same to oversee as the first.
Most companies run a dozen tools, each with its own admin console. Answering "who can see this" means asking twelve times.
Who can reach what
Roles across the group, and the applications each one reaches
| Role | Expense Claims | Purchase Approvals | Vendor Master | Leave & Absence |
|---|---|---|---|---|
| Finance Controller | Full | Full | Full | Read |
| Finance Analyst | Full | Read | Read | Read |
| Cost Centre Owner | Read | Full | None | Read |
| Field Supervisor | Read | None | None | Read |
| Employee | Read | None | None | Read |
Sign-in, group-wide
- Sign-in
- SAML single sign-on
- Directory
- Group Entra ID
- Second factor
- Required, all roles
- Session
- 8 hours, then re-auth
Won't my data end up in fifty silos?
Data from every application BuildPad generates comes together in one reporting layer, operational and management both. It is the most common objection to tailored software, and this is the answer.
Group operations report
Assembled from four applications · Q3
Subsidiaries, regions, departments.
xAppHub carries multi-layer tenancy through subsidiaries, regions and departments. An org chart's worth of nesting, managed without a separate instance per unit.
The parent organization holds twelve group-wide applications. Under it sit three subsidiaries: Singapore with nine, Malaysia with seven, and Indonesia with six. Under each of those are the departments that own applications of their own. Every level is managed from one xAppHub, with no separate instance per unit.
Frequently asked questions
What is BuildPad?
BuildPad is our AI rapid application development platform. We are a software company in Singapore. It has three parts: a Marketplace of finished applications we have already built, a Dev Platform where one of them is tailored to your business, and xAppHub where you run and govern all of them.
What can you build with BuildPad?
BuildPad builds internal business applications: approval workflows, case management, registries, external portals, operations tracking, scheduling, and many more. Check out our Marketplace for app foundations and templates that are ready to be personalized for your business. We can also create ones from scratch for those we haven't covered.
How long does it take to build an application with BuildPad?
A BuildPad application built from one in the Marketplace typically takes two to six weeks. Each listing carries its own estimate, so check the one you would start from. It is weeks rather than quarters because the infrastructure, data model, roles, audit and deployment already exist before the build starts.
How much does BuildPad cost?
BuildPad is priced per organization, not per seat. The number is set by how many applications you build, how many people use them, and how much you want us involved. It costs the same or less than the subscription it replaces, and you own what you get.
Why build internal tools instead of buying software for them?
Buy off-the-shelf software when your process looks like everyone else's, and build with BuildPad when it does not. Teams whose process diverges bend it to fit the tool, buy a second tool for the gap, and renew anyway because migrating costs more. BuildPad gives you an application shaped around how you actually work, in weeks.
What does BuildPad generate?
BuildPad generates the whole secured stack, not just the screens. UI: pages, forms and tables built from your schema. Logic: workflows, server-side rules and scheduled jobs. Data: collections, relations, roles, policies and an audit trail. Interface: a typed DaaS client, REST endpoints, authentication and file handling.
How is BuildPad different from other AI coding tools and app builders?
BuildPad follows a fixed method instead of open-ended prompting: requirements, then design, then tasks, each approved before any code, then a build in six tested phases. It generates the layers underneath the screens rather than a front end over a hosted database, and it assembles proven modules rather than regenerating them.
Who owns the code BuildPad generates?
You own the code BuildPad generates, outright, in your own git repository. That holds whether your own team runs the build or one of our forward deployed engineers builds it alongside you. UI components are copied in as editable source rather than imported from a package, so nothing stops you maintaining it without BuildPad.
Is BuildPad secure enough for government and regulated work?
BuildPad generates the security model rather than leaving it to be added before launch, which is what makes it usable for government and regulated work. Role-based access control, policies, permissions, field and record level rules, workflow controls and audit logs are enforced on the server and infrastructure.
How do I get started with BuildPad?
Book a demo and we walk you through the platform against your own case, including what it would cost. From there your own team can run the build, or a forward deployed engineer can learn how your business works and build it alongside you. Same platform, same ownership either way.