Tables and relations Views per team Visual automation REST API and code
What it is for

Sales, operations, projects, whatever you actually run

You make a space for an area of the business and tables for the things in it. CRM with clients and contacts. Sales with deals and leads. Finance with invoices and vendors. A client portal that shows people outside the company only what you want them to see.

Then you get one place to see all of it: what changed and who changed it, what is assigned to you, what needs attention, and the numbers you care about.

The InfoLobby overview: a tree of spaces and tables on the left, a live activity feed in the middle, and open tasks, flow errors and pinned reports on the right
More than rows

A record is not just a row in a table

Open a project and the work around it is already there. This is the part people miss when they picture a database, and it is usually the reason the spreadsheet stopped being enough.

  • Tasks with an owner, a due date and a reminder that actually fires
  • Comments, so the decision is kept next to the thing it was about
  • Files attached to the record they belong to
  • Full history of what changed and who changed it
An InfoLobby project record showing its fields and an attached proposal PDF, with Comments, Tasks and Activity tabs beside it and a live comment thread
What you get

Tables, views, forms, automation, permissions and an API

Not a category, a set of parts. You assemble them into the system your business actually runs on, and you keep rearranging them afterwards.

Structured data

Real field types, relationships between tables, and rollups. Not a grid of text.

A view per team

Grid, kanban, calendar and gallery over the same records, with permissions per space.

A way in and out

Public web forms, embeds, inbound email, webhooks, scheduled flows and a REST API.

Reports

Charts and summaries over live records. No export step and no stale copy doing the rounds.

Moldable by design

Change it the day the process changes

You are the one who knows how the work actually runs. You should not have to file a ticket with anybody, including yourself, to reflect that.

  • Add a field, a status or a relationship in seconds
  • Restructure a table without a migration project
  • Change a workflow without redeploying anything
  • No vendor roadmap to wait on, no rebuild to schedule
InfoLobby field designer, adding and reordering fields on a table
The InfoLobby PHPScript editor, writing custom logic inside a flow
No wall

When the builder runs out, you keep going

Most of InfoLobby is configuration. We do not pretend every requirement fits inside a drag and drop interface, so there is a way through when yours does not.

  • PHPScript for logic the visual builder cannot express
  • Call any REST API from a flow, or receive webhooks into one
  • A full public REST API over your own data
  • Bring your own keys for SMTP, OpenAI and other services
  • Optionally connect your own MySQL server or S3 storage

Read the API docs before you sign up →

Managed infrastructure

You build it. We run it.

Building the system is the interesting part. Patching a database server at 2am is not. Every account comes with the infrastructure already running.

Managed MySQL

A real database, provisioned with your account. Nothing to install or maintain.

File storage

S3 storage for the documents your workflows depend on.

Outbound email

Send from flows and forms without standing up your own mail server.

Backups and updates

Handled for you. There is no deploy step and no version to upgrade.

Your data stays reachable either way: full REST API access, and SQL dumps you can download whenever you want.

Automation

Automate the process, not one app

Flows run on record changes, schedules, form submissions and inbound webhooks, and they reach across every table in the workspace rather than one silo.

  • Update records and create related work
  • Send email and generate documents
  • Call external APIs and use AI
  • Drop into PHPScript for the awkward cases
The InfoLobby visual flow builder with a multi-step automation
Pricing

Flat monthly pricing. Not per seat.

The moment a system is useful, you want everyone on it. Per-seat pricing punishes you for exactly that, so we do not charge it.

Unlimited users Every plan. Add the whole team, contractors and read-only people without doing the maths first.
Infrastructure included Managed database, file storage and the automation builder come with the plan.
No feature gates The API, webforms, automation and PHPScript are not held back for an enterprise tier.
App Market

Start closer to done

A blank workspace is the worst part of any tool like this. Install something that already works, then pull it apart until it matches how you operate.

Browse App Market
Install Get working tables, views and flows on day one.
Adapt Change the fields, views, forms and automation to fit.
Operate Run the work without adding another tool to the stack.
How it works

Start with one process. Add the next when it belongs together.

Do not architect the whole company on day one. Take something the team already does, put it in, and let it grow from there.

1

Get something live

Import your data, build a table, or install an App Market pack.

2

Make it fit

Add the fields, views, forms and permissions the work actually needs.

3

Take the manual work out

Add flows, call APIs, connect services, and script the parts that need it.

Fit

Who this is actually for

InfoLobby suits people who want to shape the system themselves. That is a real preference, and it is not everybody.

Choose InfoLobby if

  • You are the person everyone asks to make the system do something new
  • Your process is specific enough that no off-the-shelf app quite fits
  • You want to build it yourself and keep changing it
  • You want an API and a code escape hatch for when configuration runs out
  • You are tired of paying per seat for people who only need to look

Do not choose InfoLobby if

  • You want a deep vertical suite with every industry feature pre-built
  • You want someone else to design your workflow for you
  • You need a pure CRM with dialers, enrichment and sales coaching
  • You are not willing to shape any part of the system yourself

Common questions

What happens when I hit a limit?

You go through it. PHPScript handles logic the visual builder cannot express, flows can call any REST API, and the public API reaches your data from outside. The builder running out is not the end of the road.

Do I need to write code?

No. Most of InfoLobby is configuration, and plenty of workspaces never contain a line of script. Code is there for the day you want it, not a requirement for getting started.

Can I get my data out?

Yes. Everything is reachable through the REST API, and you can download SQL dumps of your database whenever you like. You are not writing your data into a box you cannot open.

Do you charge per user?

No. Plans are flat monthly and include unlimited users, so adding the rest of the team, your contractors and read-only viewers does not change the bill.

Do I have to start from scratch?

No. Import the data you already have, install an App Market pack and modify it, or connect an existing service and build outward from there.

Can I use my own database?

You can connect your own MySQL server or S3 storage if you want to. Most people do not bother, because the managed ones are already running and there is nothing to maintain.

Build it the way you actually want it

Start with one process. Change it as often as you like. Nobody is going to tell you the roadmap does not allow it.

Start Free Trial Explore the app →

14-day free trial. No credit card required.