Your business,
as software.
Build the system your business runs on: your own lists, forms, permissions and automatic steps, without hiring developers. Try every change in a safe copy before it reaches the version your team uses every day.
Quoted
Booked
Invoiced
3 changes to review
- Add a "Quoted" stage
- Track parts used per job
- Send an invoice when a job is done
Everything your team needs, built by you
Set up the lists, screens and rules your business actually uses, instead of bending your business around a standard tool.
Your own lists and forms
Customers, jobs, tickets, anything you keep track of. Choose from 25 field types, fill in records with forms, then search and filter. Bring in what you already have from CSV or Excel.
Who sees what
Roles and permissions that go all the way down to a single field. For example, the office sees prices and the field team does not.
Automatic steps
Draw your workflows visually: when a job is done, send the invoice.
Portals for outside people
Give customers, tenants or partners their own pages.
Dashboards and menus
Key figures at a glance, and menus arranged the way your team works.
Live updates
Screens update on their own as records change.
Connect to other services
Here is what has been tested and what has not.
Ready-made connector presetsBeta
Presets for Slack, e-conomic, Uniconta, UiPath Orchestrator, e-signatur, Twilio and Microsoft 365 mail. They are built but not yet tested against the real services.
Any other web service
A generic web-request step lets a workflow talk to other services. It has been tested against a stand-in service.
Incoming messages
Other systems can call your workflows through incoming webhooks signed with the Standard Webhooks method. Services that sign in their own way, such as GitHub, Slack, Stripe and Twilio, cannot call them yet.
Passwords and keys for connected services are saved by an administrator, kept in a vault and never shown again.
Start from your industry
Four templates, each with invented sample records you can load, look at and change.
Field service
Customers, sites, jobs and visits.
Sales CRM
Companies, contacts, deals and activities.
Help desk
Categories, customers, tickets and replies.
Property management
Properties, units, tenants, leases and maintenance requests.
Save your own changes as your own template. Some example workflows in the templates use connector presets, which are in beta.
See the templatesTry it first. Go live when you are sure.
Changes are made in a safe copy and move to the version your team uses only when someone chooses to move them.
Dev, Test and Live
Each environment keeps its records in its own database schema or its own database. Work in Dev, check in Test, then promote to Live.
Plan, review, apply, revert
You plan a promotion, go through every difference sorted by risk, apply it, and can revert it later.
Deletions are named one by one
Anything that deletes something has to be named and confirmed item by item.
Out-of-date plans are refused
If the system changed after a plan was made, applying that plan is refused.
A separate right to promote
Applying changes to an environment needs the promotion right for that environment. Being an administrator is not enough.
The AI proposes, a person applies
The AI can propose a tailored template. It never changes your system on its own. A person with the promotion right applies it in a separate step.
Records are copied between environments only for tables you mark as configuration, or when you explicitly choose to.
What we can show today
We only list what is true and provable.
Secrets stay in a vault
Credentials are kept in a vault, never in the database.
Support only with your knowledge
Our support staff can only enter your environment through a session with a stated reason and an end time. You can see the session and end it.
Your own sign-in
Each company gets its own sign-in, and links between records can only point to your own company's records.
Installable offline
The product can be installed without an internet connection.
Planned · not available today
On our roadmap: AI that proposes, you approve
We are planning AI features to make Tilebench simpler to use. None of them are available yet.
Describe a change
Write what you need, for example "add suppliers, linked to orders, with a rating". You get a proposed change with a reason for each part, to review before anything happens. We plan to start with tables and fields.
AI decisions in workflows
Add a step that sorts, scores or answers yes or no about a record, with a confidence level. The workflow can take a different path based on the answer, for example sending unclear cases to a person.
AI writing in workflows
Summarize a record, draft a reply, or pull values out of text into fields, as a step in a workflow.
Connection helper
Describe an integration, and Tilebench suggests how the other system's data maps onto your fields.
Works with your AI assistant
Through MCP, the open standard for connecting AI tools, an assistant such as Claude could work in a Tilebench application with your own permissions, to read data and propose changes. Assistants work with your records only in environments where your administrator allows it. Every change is approved by someone who is allowed to make it.
Bring your own AI model
Choose which AI models your organization uses, including one that runs on your own servers. Assign a model to each job (design help, decisions, writing), or switch the default model off.
You stay in control
The same rule applies to every AI feature we plan: AI proposes, a person decides.
You approve every change
Every AI change to the data model is shown as a reviewable change, is approved by someone who is allowed to make it, and can be undone like any other change.
AI never has more rights than you
AI never gets more permissions than the person using it.
Design help sees names, not records
When AI helps design the model, it sees only table and field names, never records.
Your data reaches a model only if you allow it
Record data reaches an AI model only in an environment where an administrator has turned that on, and only the fields each step lists. Each such use is logged. Assistants you connect are covered by the same switch.
Details may change.
Questions and answers
Do I need developers?
No. The point of Tilebench is that you build your own internal system without hiring developers: your own lists, forms, permissions and automatic steps.
What can I build?
Lists such as customers, jobs and tickets, forms, rules for who can see what, automatic steps, pages for outside people and dashboards with key figures. Four industry templates give you a start.
Can the AI change my system on its own?
No. The AI only writes a proposal. A person with the promotion right applies it in a separate step. The plan lists every difference sorted by risk, deletions have to be named one by one, and a plan that is out of date is refused.
Which AI features are planned?
Today the AI proposes a tailored starting template from a few questions about your business. Choosing your own AI models, describing a change in plain words, AI decisions and AI writing as workflow steps, a helper for mapping other systems' data onto your fields, and working with your own AI assistant through MCP. They are on our roadmap and not available today.
Does AI get to see my data?
That is your decision. When AI helps design your model it sees only table and field names, never records. Record data reaches an AI model only in an environment where an administrator has turned that on, and only the fields each step lists. Each such use is logged. The same goes for assistants you connect.
Can I try a change without affecting the version my team uses?
Yes. Build and check changes in Dev and Test, which keep their records separate from Live. A change reaches Live through a promotion, which needs the promotion right for Live, and you can revert it afterwards.
Can I bring in my existing data?
Yes, from CSV or Excel files.
Does it work with the other tools we use?
There are ready-made connector presets for Slack, e-conomic, Uniconta, UiPath Orchestrator, e-signatur, Twilio and Microsoft 365 mail. They are in beta and not yet tested against the real services. A generic web-request step connects to other web services.
Which languages does it support?
The product is in English today. This website is available in English, German, French and Italian.
Is it available today?
Tilebench is in preparation. The product works today. Request access and we will be in touch.
What does it cost?
Pricing has not been decided yet, so we do not publish any.
What about security and compliance?
We only state what we can show today: credentials are kept in a vault, support access is limited in time and visible to you, and each company has its own sign-in. We do not make claims about certifications or legal compliance yet.
Request access
Tell us about your business and what you would like to build.