New: sign-offs with password re-entry, and notifications

Custom software, built by your AI, owned by you.

Describe your process in Claude, ChatGPT or Codex. Get a real app with roles, approvals and an audit trail. Run it in our cloud or yours.

An audit app's dashboard with a notification that an engagement is ready for sign-off

AuditDesk, generated from one description. Sample data.

Built from the assistant you already use

ClaudeClaude DesktopChatGPTCodex
How it works

From a prompt to an approved request. Same day.

Real screens from the Requests sample: an employee asks, a manager decides, the app keeps the record.

01

Describe it in your assistant

Build me a Requests app. Employees submit purchase, equipment, travel and time-off requests. Managers approve or reject them with a note. Employees only see their own requests. Keep a history of every step, and notify the manager when something is submitted and the employee when it's decided.
02

Review the plan before it's built

Who can do what, the steps a request moves through, who gets told.

The plan preview: who can do what, the request steps, and the notification rules
03

The manager approves in the app

Marcus is told a request needs him. He approves it with a note.

A manager approving a request with a decision note
04

Every step is on record

Who submitted, who approved, and when. Emma is told it's approved.

The request's status history: drafted and submitted by Emma, approved by Marcus

Watch a full build: ClaimKit, live in four hours →

Where it runs

Run it where your data must live. Leave whenever you want.

QuestionOur cloudYour cloudYour machine
Who runs itNeoApps, on Microsoft Azure in the USYou, on your own servers
UpdatesWe keep it running and up to dateYou
Your app's codeYes, anytime. Ask your assistant for your app's plan and build it with the open-source generator.Yours
Your recordsExport any list to CSVIn your own database
PriceFrom US$49/monthFree, open source
Start buildingDeveloper setup
  • Encrypted in transit and at rest
  • Roles enforced on the server
  • Audit trail
  • Password re-entry for sign-offs
  • We never train on your data
  • Open source

SOC 2 and HIPAA are not certified yet. Read the FAQ

Production grade

Your rules, enforced on the server.

Not hidden buttons. Every request is checked, for every person, every time.

Sign-offs that hold up.

The partner re-enters their password to sign. Their name, the time and the statement go in the audit log. Admins can't skip it. The AI can't sign.

A sign-off dialog asking the partner to re-enter their password, showing the statement being signed
A roles and permissions grid showing what each role can read, create, edit and delete

Who sees what. Who changes what.

Set it by role. Customers see only their own records. Records lock after sign-off. The server enforces it, not the screen.

A history for every step.

Who moved it, from what, to what, and when. Ready when the auditor asks.

A signed-off engagement with its phase history listing each change and its time
Everyday use

Works the way your team does.

On every screen.

Add it to your phone's home screen or install it on your desktop. Notifications in the app, or by email.

The app on a phone, showing the dashboard

Your data is never stuck.

Export any list to CSV. The code is open source. Leave whenever you want.

A list of engagements with search and an Export button
Proof

ClaimKit: years of R&D tax-credit expertise, live in four hours.

Our team built ClaimKit, a full client portal for R&D tax-credit consultants, with a coding agent and NeoApps in about four hours. A typical agency build takes five to six months.

The expert still decides. The app does the intake, documents and evidence.

Replace one spreadsheet this week.

Start with one team and one workflow. Add the next when it sticks.