Some Form Elements
hs-form
form-columns-1
form-columns-2
hs-form is main form class.
form-columns-1 is class of wrapper with 1 column for inputs.
form-columns-2 is class of wrapper with 2 columns for inputs.
input and label
hs-input
Field Description / Help text
hs-field-desc
This is help text for the field
Field error message
hs-error-msgs inputs-list
hs-error-msg
  • Error message label
hs-error-msgs inputs-list is an HTML list element.
hs-error-msg is a text span inside HTML List Item element.
Text area Input
hs-input hs-fieldtype-textarea
hs-fieldtype-textarea is added as combo class.
Checkboxes
hs-form-booleancheckbox
hs-form-booleancheckbox-display
inputs-list
hs-input
Note: HubSpot uses basic HTML checkboxes, Webflow checkboxes work differently than the default HTML checkboxes, hence in order to style HubSpot checkboxes you need custom CSS.
you can use Webflow checkbox to style and then copy CSS from it.
Radio Buttons
inputs-list
hs-form-radio
hs-form-radio-display
inputs-list
hs-input
Success message
submitted-message
RecaptCHA
hs-recaptcha
Submit button
hs_submit
hs-button
Oops! Something went wrong while submitting the form.

Take your vibe-coded app safely into production

You’ve built an app with Lovable, Claude Code, or a similar tool, but you’re not sure it’s safe to use with real business data. Convert it to Appfarm and put it into production with the security your IT team requires.

Convert your app
Book a call

Most vibe-coded apps never get connected to real business data

You’ve put real time into what you built, and people are already asking to use it. The trouble starts when it needs access to customer or project data, or when someone asks who’ll look after it.

01

You have no clear path to production

Sign-in, access rules, hosting, uptime, and performance are left for you to work out on your own.

02

It can’t connect to approved systems

IT won’t let a prototype near the ERP, the CRM, or customer data, and they have good reasons for that.

03

You can’t see how it really works

The app was written from prompts, so even the person who built it may not know how it calculates a figure or decides who gets to see which records.

04

It’s hard to work on together

Usually one person built it, and nobody else can pick it up when they’re away.

05

There’s nobody to call when it breaks

If it stops working on a Monday morning, you have to fix it yourself.

Three steps from prototype to production

‍

1

Show us your app

Tell us what it does and give us a demo. If it’s a good fit, we’ll ask for the code or access to the project.

2

We import it into Appfarm

We create a detailed spec of your app and rebuild it with Appfarm’s building blocks, so it looks and works the way it does today.

3

Keep building and go live

Carry on prompting or build visually, connect it to your systems, and deploy it with sign-in through your identity provider.

What changes in Appfarm

The same app on a platform your IT team can approve

‍

Visual verification and control

See exactly what the app does on the visual canvas, and change it there or with a prompt.

Secure deploy to production

Publish with sign-in through your identity provider and role-based access control.

Governed integrations

Connect to your ERP, CRM, and other systems through integrations your IT team can review and approve.

Live collaboration

Several people can work on the same app at the same time, so it no longer depends on one person.

Support and accountability

Appfarm runs the platform, keeps it up to date, and helps you when something goes wrong.

Convert your app today

Tell us a little about what you’ve built, and we’ll get back to you about importing it into Appfarm within one working day.

Would you rather talk first? Book a call with us.

‍

Trusted by industry leaders

Get in touch