A business app platform, built by hand or with AI

Let anyone build business apps. With guardrails your security team sets once.

People build what they need, by hand or with AI, inside the permissions your admins already set. Sign-in, isolation and hosting are the platform's job, so reviewing a new app means checking its permissions and rules, not its sign-in, hosting and code.

Redforge

Build

Applications Tables Business rules Workflows Portal pages Test suites

Tools

Reviews Catalog

Monitor

Run history Access log

Applications / Discount approvals

branch: first-draft

Discount approvals

Created with AI by Sales ops · 4 minutes ago · prefix acme_discount

Overview Tables Pages Permissions

tables

rules

workflow

portal pages

4/4

tests pass

TableWho may readWho may change

acme_discount_requestsRequester, sales managersRequester (own, while pending), sales managers

acme_discount_accountsSales teamSales managers

acme_discount_limitsSales teamFinance

Ask AI

Reps should be able to ask for a discount over 10%. Their sales manager approves, and reps see their requests on a page.

Read groups · Read help: permissions · Read help: portal pages

Plan · 9 steps

create table acme_discount_accounts

create table acme_discount_requests

create rule one-pending · before save

create workflow notify-manager · run as Sales

create page my-discounts · signed-in staff

+ 4 more: permissions, tests

Confirm planShow full arguments

AI use this month: 21% of the budget, included

Merge request #3 Awaiting review

AI reviewRequesters can update their own request after approval. Limit updates to pending requests?

You opened this request, so someone else has to approve it.

Guardrails

A web app has to get forty things right. On Redforge, your app only supplies four of them.

Most AI app builders generate a whole app, sign-in and database access included, and nobody reviews it. Here you build only what's specific to your app, by hand or with AI. Everything that keeps it safe is the platform's, tested once and shared by every app. Your organization works in its own private tenant.

Logins, passwords, backups and keeping your data private are handled for you.

In every appWritten by

Sign-in, two-step verification, sessionsPlatform

Password storage and rate limitsPlatform

Keeping one tenant's data from anotherPlatform

Checking permissions on every queryPlatform

Escaping output, CSRF, content security policyPlatform

Secrets and API tokensPlatform

Hosting, backups, access logPlatform

Tables and columnsYou or AI

Which groups may read and change themYou or AI

Rules and workflow scriptsYou or AI

Page templatesYou or AI

Branches, review, releases

Change your app without breaking the one people are using.

Most tools keep changes away from live data only with separate environments, a pipeline or a developer. On Redforge, anyone who edits an app, by hand or with AI, works in a branch, a private copy they can't break, and changes reach production only through review and a release.

Discount approvals / Historyproductionbranch first-draft

Tue09:12

Opens a branch

A full copy of the app and its groups. Schedules don't run, webhooks can't leave, and nobody's access can widen.

Sales ops

Tue09:20

Adds the discount tables and a rule

From a plan Sales ops confirmed, showing every value it would write.

Tue10:02

Changes the rule by hand

They ask for a one-line change, check it and save.

Sales ops

Tue10:05

Runs the saved tests

Each rule runs against sample rows. 4 of 4 pass.

Platform

Wed09:40

Approves the merge request

Someone other than the author approves, unless your admin allows self-approval for small teams. Your admin chooses the reviewers. An AI review can comment, never approve.

Sales manager

Wed10:40

Ships the first release

Releases are frozen. Production only changes by applying one.

Sales ops

Ask AI in the code editor

Select the lines. Say what should change.

Most rules start as a sentence. When one needs changing, select the lines and say what should change.

Ask: Don't let a rep send a second request for the same customer while one is still waiting.

The rule it wrote

def main(data):
    if data["acme_discount__status"] != "pending":
        return data
    waiting = as_user.list("acme_discount_requests", {
        "acme_discount__requester": data["acme_discount__requester"],
        "acme_discount__customer": data["acme_discount__customer"],
        "acme_discount__status": "pending",
    })
    if waiting:
        fail("This customer already has a request waiting.")    return data

What AI can't do

Limits you don't have to trust a prompt for.

Read or change tenants, admins, quotas, usage or any field marked hidden.

Do anything the person asking couldn't do in the console themselves.

Change anything without a confirmed plan, or apply one twice.

Approve a merge request. Its review is advice, stored as text.

Spend past the tenant's monthly budget. Usage is shown under every message box.

Who it's for

For the business without a developer, and the one with a security office.

Small and mid-sized businesses

You know exactly
what the app should
do. You just can't
write it.

Ask for it, check the plan, use it the same afternoon. Customer portals, internal tools, approvals, inventories: whatever your business runs on, with sign-in and permissions you didn't have to think about.

Starter apps

Project management

Run agile sprints, waterfall phases or kanban boards from one app.

Requests and approvalsComing soon

Your own approval rules, such as discounts over 10% going to a sales manager, with a record of who approved what.

Client intake and case trackingComing soon

Clients or residents submit through a portal, staff work each case through your own steps, and each person sees only their own cases.

Inspections and complianceComing soon

Checklists that change with the site or the rule set, with findings, follow-ups and sign-off.

Public sector and enterprise

The people who know the work are already building their own apps. Give them somewhere safe to do it.

Instead of personal accounts and AI-generated code with keys in the browser, they build in your tenant, behind your sign-in, through your review. IT sets the guardrails once and keeps control without writing every app. Run it on a dedicated stack in Canada.

For CIOs and platform owners

For the CIO who has already paid for one platform rollout.

If the last one came with a licence audit, a two-year partner engagement and an upgrade nobody dared apply, and now people across the business are building their own apps around it anyway, this is what we did differently.

What you're used toWith Redforge

Apps built by staffBuilt on personal accounts, keys in the browser code, a database open to the internet, nobody reviewing.Built in your tenant, behind your own sign-in through Entra ID or another OpenID Connect provider, and shipped only through a merge request someone else approves.

SprawlHundreds of apps across environments, and nobody can say what's in production.Each application page lists everything inside it. Production is merge-only after the first release.

Change controlBranches and reviews exist, but they need a developer, a pipeline or an enterprise plan.Every change, by a person or AI, is made in a branch, reviewed in a merge request and shipped as a frozen release.

ImplementationA partner engagement before the first form goes live, and another every time it changes.Your own people ask for changes and review them. Rules are short scripts they can read and test.

UpgradesUpgrades that break customizations, so you skip them and fall behind.Your applications change only when you approve a release. Their saved tests rerun to show nothing moved.

LeavingYour data in a proprietary model, out only through a migration project.Every table is a real Postgres table. Your data is yours: export any table as CSV, any day. Your apps run on Redforge.

Ask for your first app today.

See how it builds, with review and release included. If it doesn't work out, export your tables and go.

Let anyone build business apps. With guardrails your security team sets once.

A web app has to get forty things right. On Redforge, your app only supplies four of them.

Change your app without breaking the one people are using.

Select the lines. Say what should change.

Limits you don't have to trust a prompt for.

For the business without a developer, and the one with a security office.

You know exactly what the app should do. You just can't write it.

The people who know the work are already building their own apps. Give them somewhere safe to do it.

For the CIO who has already paid for one platform rollout.

Ask for your first app today.

You know exactly
what the app should
do. You just can't
write it.