Company login on every app
Every request needs a company login. There are no public links.
For operations teams who build their own tools
Building is easy.
Building is easy.
Deployment is not.
Your team built the tool with an AI coding agent. Putting it behind company login, with a database, secrets and an IT sign‑off, is the hard part. We handle that.
Private pilot. Not generally available yet.
Inside every address
Company login on every request. Only the people you share it with get in.
How it works
One command to a link your team can open.
Deploy from the folder you built in. The cloud account, the login and the upkeep are ours.
~/dock-boardssc deploy --app dock-board --waitPacked 41 files.Built R3. Deploying it to preview.R3 is live in preview of dock-board.Preview: https://dock-board--preview.k4r7tq2m.delimitusapps.comssc promote dock-board --waitprod of dock-board runs R3.Prod: https://dock-board.k4r7tq2m.delimitusapps.comssc share dock-board "Inbound team" --groupShared prod with Inbound team as user.
The gap
It works on your laptop. Now what?
Between a tool that works and a link the night shift can open sits a list nobody on the floor signed up for.
A cloud account
Someone sets it up, pays for it and keeps it apart from everything else.
Company login
Only staff get in, and people who leave lose access with their account.
Secrets
The carrier’s API key can’t live in the code or in a shared sheet.
A database
Backed up, and not shared with every other tool in the building.
An IT review
Security wants to know what it reaches and who can see it.
Someone to keep it running
Updates, logs, and the call when it stops at 2 a.m.
So the tool stays on a laptop, or goes back to a spreadsheet. Delimitus is that list, done.
Example
From a laptop to the night shift.
Dana runs inbound at a distribution centre. She built a dock board with Claude Code. This is what her team opens after one deploy.
Who’s looking?
Shared with two groups from the company directory. Everyone else is turned away.
dock-board.k4r7tq2m.delimitusapps.com
Company login
DOSigned in as Dana Ortiz, through Inbound team
Inbound dock board
Reno distribution centre · today
Trucks due today38
Unloaded2155% of today’s trucks
Running late4
| Door | Carrier | Booked | Status |
|---|---|---|---|
| D04 | Example Freight Co. | 06:30 | Unloading |
| D07 | Sample Linehaul | 07:15 | 40 min late |
| D11 | Demo Carriers | 08:00 | At the gate |
| D02 | Placeholder Haulage | 08:45 | Expected |
Showing 4 of 17 doors, earliest booking first.Shared with Inbound team, Night shift
Illustration · example data
Works with
Build with what you already use.
Delimitus doesn’t write your app. It runs the one you built.
Build with
- Claude Code
- Codex
- Cursor
- Lovable
- Replit
Python and Node apps, from a folder or a GitHub repository.
Runs on
- Google Cloud
In the US, with each company in a cloud account of its own.
Sign in with
- Google Workspace
- Okta
Your people use the company login they already have.
Product names belong to their owners. Delimitus is not affiliated with or endorsed by them.
What you get
Everything between the laptop and the link.
The tools operations teams build, and what each one needs to go live.
A dock scheduler the inbound team books trucks into.
Built withClaude Code
- Its own database for the bookings
- A timer that rolls the schedule over at midnight
- Shared with the Inbound team group
For the people who build
- Deploy from a folder or a GitHub push
- An address behind company login
- Share with a person, a group or the whole company
- Preview and production
- Roll back to an earlier release
- Logs
- A database for each app
- Timers for scheduled jobs
- File storage
- Secrets, kept out of your code
- Read-only access to company databases
- Internet access to the hosts IT allowed
For IT
- A list of every app and who owns it
- One switch that turns an app off
- An audit log of every change
- Approvals before production
- Each company in a cloud account of its own
- Coding agents held to the same rules as people
PilotAll of this is part of the private pilot offer.
Cost
What doing it yourself costs.
A year of running internal apps behind company login: the cloud bill at list prices, and the IT time it takes. Change the numbers to match your team.
| Item | Do it yourself | With Delimitus, we take over |
|---|---|---|
| Cloud bill, list prices | $2,738 | The cloud account and everything in it |
| IT setup, one time | $5,440 | Company login, secrets and the database |
| IT time to put each app live | $8,160 | The deploy; your IT approves |
| IT upkeep, 12 months | $16,320 | Keeping it running |
| Total | $32,658 | Pricing is agreed with each pilot |
Defaults: 10 apps, $68 an hour, 80 hours of setup, 12 hours per app, 2 hours of upkeep per app a month. The hours are our estimate; change them.
Where the numbers come from
Cloud: Google Cloud list prices for us-central1, in US dollars, 730 hours a month, no free tiers and no discounts. A month costs $129.53 plus $9.86 for each app:
- HTTPS load balancer for company login, $18.25 ($0.025 an hour). Cloud Load Balancing pricing, fetched 2026-10-07.
- Managed Postgres, smallest high-availability tier with point-in-time recovery, $102.02. Cloud SQL price list, fetched 2026-10-07.
- A fixed outbound IP address, $4.67. Cloud NAT price list, fetched 2026-10-07.
- Logs, 5 GB a month, $2.50. Secret store, 20 secrets, $1.23. Builds, 60 minutes, $0.36. Image registry, 5 GB, $0.50. Price lists fetched 2026-10-07.
- Each app: one instance kept warm so the first visit is not slow (minimum instances 1; 1 vCPU, 512 MiB), $9.86: $6.57 for CPU and $3.29 for memory. Cloud Run pricing (cloud.google.com/run/pricing), idle minimum-instance rate, fetched 2026-10-07.
IT rate: $47.66 an hour, the median pay of network and computer systems administrators (US Bureau of Labor Statistics, 2025), times 1.43 for benefits, because wages are 70.0% of what private employers pay per hour worked (BLS Employer Costs for Employee Compensation, June 2026). That is $68.15; the default rounds it to $68.
Hours, our estimate: 80 to set up the cloud account, network, company login, build pipeline, logs and a security review; 12 to put each app live; 2 a month per app for updates, access changes and fixes.
Security
Locked down by default.
Walled off
An app can’t reach other apps. It reaches the internet only where IT allowed it.
Secrets stay secret
Stored for the app and never shown again, to people or to coding agents.
Checked before it ships
Every build is checked for leaked keys before it goes live.
Limits
What it doesn’t do.
Some things are left out on purpose.
- No public appsEvery request needs a company login.
- No custom domainsApps live at an address on our domain.
- No inbound webhooksOutside services can’t call into your app.
- Company data is read-onlyApps read your company databases and never write to them.
Questions
What does it cost?
Pricing is agreed with each pilot. The cost section shows what doing it yourself costs.
Which tools can I build with?
Claude Code, Codex, Cursor, Lovable and Replit. Python and Node apps, from a folder or a GitHub repository.
Where does it run?
On Google Cloud in the US, with each company in a cloud account of its own.
Who can open my app?
Only people signed in with your company login, and only the ones you shared it with: a person, a group, or the whole company.
Can an app be public?
No. Every request needs a company login.
What happens to my code and data?
Your app runs in your company’s own cloud account. It reads company databases read-only and reaches the internet only where IT allowed it. Secrets are never shown again, to people or to coding agents.
How do I get in?
Delimitus is in private pilot. Request a pilot below.
Private pilot
Ship the tool your team already built.
Delimitus is not generally available yet. Tell us who you are and we’ll reply by email.
Thanks. We have your request.
We’ll reply by email.