Turn your idea into a web app your customers and teams can use.
Build visually or bring your own AI. Connect your data, automate the work
and give every role the right view.
Your AI designs the experience.PBS runs it.
Build a people app with leave requests, manager approvals and a team dashboard.
A demonstration. No live changes.
Connect your own API key.
Keep your options open.
For founders, turn your business idea into a customer portal, a subscriber experience or the operational tools behind your venture. Test the design, learn from users and keep refining it.
For IT teams, deliver the systems your organisation needs with reusable components, explicit permissions and a controlled path from draft to release.
Explore AI-assisted buildingGive office teams a focused workspace, managers live dashboards and customers a secure portal. Each runs on the same data, permissions and business processes, with a view designed for every role.
Shared data, permissions, automations and APIs. The right view for every role.
Connect your OpenAI, Claude or Gemini API account. Describe a web app by prompt or voice. PBS turns the proposal into a validated design for your team to review, refine and publish.
See how PBS handles a new app request, a permission change and an unsupported code request. Each proposal is checked before it can affect your draft.
Change a validated design while the platform provides the runtime. Reduce the per-application burden of generated source code, duplicated UI components and bespoke infrastructure.
Inspect the proposal, preview the result and apply it to a draft. Access and destructive changes need review. Publishing stays in your hands.
Use your own API account. Set request and token budgets. Refresh PBS’s knowledge as the platform evolves.
Your design context goes to your chosen provider. Live records and credentials are excluded from the builder context. Provider API charges are separate. Knowledge refresh supplies schemas and examples; it does not retrain model weights.
Design complete business applications: connected data, role-specific experiences, automated decisions and actionable reporting.
Define fields, validation and relationships. Add role-controlled record lifecycles and independent field state machines, with project-specific states and allowed transitions.
Compose pages and forms with tables, calendars, maps or Kanban. Add buttons and links with JavaScript / TypeScript IntelliSense to validate input, control fields and run permitted workflows.
Build approvals, tasks, durable waits and parallel paths. Reuse workflow packages across projects, start from ready-made rules, and trigger work from events, saved searches or schedules.
Bring your key numbers into view. Build reports your team can access, print, and export to Excel or PDF.
Delegate application administration and define user roles with object, record and field-level permissions. Give each team the access its work requires.
Add hosted checkout for subscriptions, upgrades and refunds, with entitlement-based feature access. Payment collection stays with your provider.
Keep documents, threaded discussions, notifications and QR experiences connected to the records they support. Reduce context switching across disconnected tools.
And when your app needs to reach further: generic APIs, webhooks, integrations and hosted payments.
Explore the docsGive external systems, integrations and custom front ends a straightforward way to work with PBS. A consistent POST-based API exposes your published app without a separate API project for every object.
Create, read, update, delete and search records with server-side filtering, sorting and pagination.
Execute permitted automations, check run status and read or acknowledge user notifications.
Discover branding, objects and callable automations through the self endpoint, then build a custom client or integration on the same API.
Authenticate with user access tokens. Object, record and field permissions are checked on the server.
/api/v1/apps/catalogue/searchAuthorization: Bearer <user-access-token>
{
"type": "products",
"filter": { "status": "active" },
"skip": 0,
"take": 20
}Search a permitted object using a consistent request format.
Give contracts, evidence, images and attachments a managed home alongside your application data, with storage options and access controls your IT team can configure.
Organise files in virtual folders, maintain metadata and versions, and replace content without changing its file identity. Link documents to records and use the file API from external clients.
Use S3 storage with AES-256 or AWS KMS encryption settings where supported. Store opaque, client-encrypted or password-protected files without handing their passwords to PBS.
Configurable storage protectionApply library and item permissions, use signed access for private delivery, and recover application data and files through password-encrypted backups.
AES-256-GCM backup archivesEncryption at rest depends on the storage provider and deployment configuration. Local disk requires an encrypted volume where needed. Opaque encrypted files are stored as supplied and cannot receive normal previews or image transformations. These controls do not constitute a compliance certification.
Compare delivery and maintenance costs using your own assumptions. Adjust the hours, rates and platform cost below to explore a first-year business case.
Compare one bespoke application with the same scope delivered using PBS. Adjust every assumption to reflect your project.
62% lower in this example · 280 delivery hours released
Bespoke = (build + maintenance hours) × hourly cost.
PBS = (build + maintenance hours) × hourly cost + 12 months of platform cost.
An editable scenario, not a customer result, benchmark or savings guarantee. Example hours are assumptions; the $49/month platform cost is dummy pricing from this preview. Excludes hosting, AI usage, integration services, migration, training, taxes and other project-specific costs. Apply the same scope and include those costs in a complete business case.
Explore working examples: an employee workspace, a support queue, order fulfilment and a customer portal. Switch between them to see how the experience changes.
Example experiences and sample data. Your administrators choose which apps to install and how they work.
Explore five illustrative case studies: practical ways to bring data, decisions and everyday work together with PBS.
A growing care provider needs a consistent way to coordinate staff, visits and follow-up across locations.
A care operations portal connecting service users, staff, visit schedules, documents and follow-up tasks. Managers see outstanding work; carers see their assigned visits.
Role-scoped access, scheduled reminders, document permissions and an activity history help teams coordinate sensitive operational information.
The opportunityA clearer handover between teams, with less duplication across spreadsheets.
Operational coordination only; clinical decisions and regulatory compliance require separate assessment.
HR, managers and IT coordinate onboarding by email, while employees struggle to find requests and updates.
An employee hub for profiles, leave requests, onboarding checklists and HR documents, with dedicated experiences for employees, managers and HR.
Connect related people and requests, route approvals through Flows, notify owners and report on outstanding onboarding tasks.
The opportunityOne place to request, approve and track employee services.
Payroll and statutory calculations depend on jurisdiction-specific rules and integrations.
Sales teams assemble product combinations, discounts and approvals across disconnected spreadsheets.
A quoting workspace linking customers, products, price lists and quote lines. Configure calculation policies and approval thresholds for your commercial process.
Use related objects, calculation policies, approval actions and document templates to move a quote from draft to an approved proposal.
The opportunityA repeatable quotation process with clearer pricing ownership and fewer manual handoffs.
Complex product configuration, tax and ERP synchronisation require tailored rules and connectors.
Dispatch teams chase status updates across order lists, carrier portals and customer emails.
A dispatch portal linking orders, shipments, packages and delivery events, with an exception queue and role-specific views for operations and support.
Connect carrier APIs through configured integrations, react to incoming events with Flows and notify the right team when action is needed.
The opportunityA shared view of shipment progress and a clearer path for resolving delivery issues.
Carrier tracking, labels and live delivery estimates depend on the carrier integrations you configure.
Requests arrive through chat and email, making ownership, priority and progress difficult to track.
An internal service desk for incidents, access requests and equipment, with a staff portal, an agent queue and an administrator workspace.
Categorise requests, apply role-based access, route approvals, send notifications and report on queues and response trends.
The opportunityEmployees can follow their requests while agents work from an organised, accountable queue.
Service targets, escalation policies and integrations are configured for your organisation.
Illustrative solution designs, not customer testimonials or measured results. These examples require app configuration; external services require their own connections.
Plan ownership, recovery and administration before launch. Keep your design history, choose your data setup and delegate responsibility across apps.
Keep a clear history of your app designs. Connect your own Git repository to track changes and collaborate with confidence.
Built on PostgreSQL, with backup and restore tools. Supported deployments can connect your own PostgreSQL database.
Manage multiple apps, assign app Administrators, define roles, and keep changes on a draft-to-publish path.
Review a change. Keep a history. Move forward.
PBS runs your designs on its shared runtime.
Your configuration stays distinct from application source code.
Create a workspace. Build visually, or connect your preferred AI provider using your own API key.
Explain the people, data and process. Use a prompt or voice, then refine the result in the visual builder.
Check the design and permissions. Publish when you’re ready, then keep improving as your business changes.
Tell us what your teams need to run. We’ll show you how PBS models your data, roles and approvals, and help you plan your first app.
Bring a process, a spreadsheet or a system you want to replace.
A guided walkthrough of screens, permissions and workflows that fit your teams.
Talk through a pilot, a wider rollout and the integrations you need.
Choosing the tools your business runs on should feel like an informed decision.
Go deeper in the docsNo. Your AI designs the experience, and PBS runs it. Preview proposed changes, review access permissions and publish when you’re ready. Your team refines the experience instead of maintaining a separate AI-generated codebase.
Yes. The visual builders are the foundation. Create objects and fields, compose screens and pages, configure roles, and design flows directly. AI is an optional way to create and refine the same designs.
An API key and a compatible model from OpenAI, Anthropic Claude or Google Gemini. Provider API charges are separate from PBS. A consumer chat subscription does not necessarily include API access. Connect a provider in the builder, then refresh PBS knowledge and run the compatibility test.
The server checks supported properties, design schemas, immutable IDs, permissions and draft revisions. Proposals stay within the selected scope. Sensitive or destructive changes require acknowledgement before applying. Draft changes never publish automatically. Use preview and review, and undo an AI checkpoint when no later changes conflict.
Yes. Assign users to apps and roles, and define permitted screens, objects, fields and records. Users with access to a single app land in that app directly. App Administrators can manage their assigned apps; platform administrators can manage the wider environment.
App designs can be versioned in your connected Git repository. Backup and restore tools cover configurations and data. Web apps run on the PBS server runtime, so your designs stay distinct from application source code.
No. Alongside internal tools, you can build subscriber experiences, customer portals and payment-enabled web apps. Hosted checkout supports subscriptions, upgrades, downgrades, cancellation and refunds, with entitlement-based feature access. Configure your merchant account, tax policy and verified webhooks; payment collection stays with the provider.
Yes. The generic API supports record CRUD and search, app and object metadata, permitted automation execution, run status and user notifications. Calls use user access tokens and the same server-side permissions as the app. File operations use the dedicated generic file endpoint. Build a custom client or integration against the same API.
Use the separate Data Intelligence module to define governed metrics, build reports and dashboards, and evaluate thresholds against approved PostgreSQL datasets. Optional configured AI translates questions into validated metric plans; a labelled trend baseline helps explore complete monthly history. Insight actions require explicit approval and existing app permissions. Source setup and module enablement are required; Data Intelligence does not ingest or synchronise data.
Yes. Add custom buttons and links, control field visibility, read-only and required states, and run permitted automations or record transitions. The JavaScript and TypeScript editor includes IntelliSense, type hints and diagnostics. Scripts use a restricted platform API; permissions still apply, and arbitrary network, filesystem and package access are unavailable.
Attach reusable workflow packages to selected projects, adapt ready-made rules, and configure project-specific field state machines. Combine visual steps with script operations, approvals, notifications and scheduled saved searches. The visual graph and script editor work together; they are not interchangeable whole-workflow representations.
Platform Superadmins enable App Builder and AI assistance per organisation. App permissions determine who can design, review and publish. App Administrators manage their assigned apps, and every change follows a draft-to-publish path.
No. Configure encryption with your storage provider: the S3 adapter supports AES256 and AWS KMS settings where available, while local disk requires deployment-level encrypted storage. PBS also accepts opaque encrypted and password-protected uploads under library policy, and encrypts backup archives. Opaque files cannot be inspected or previewed as normal. Encryption, access permissions and backup protection are separate controls.
The opportunity comes from reusing platform capabilities and reducing per-app implementation and maintenance. Actual savings depend on requirements, team costs, integrations and scope. Use the editable first-year comparison above with your own estimates, then include hosting, AI, training, migration and other delivery costs. The example is an assumption-based model, not a measured customer result or promised return.
No. Free, Pro and Enterprise are illustrative plans for this website preview. Prices, limits and packaging are examples, not an offer or a connected checkout. Signup buttons lead to the configured workspace portal.
From your first team workspace to a portal for every customer.
Build the business system once. Shape every view around your users.