Creator

The backbone of everything we build.

Behind a useful product, information has to move: from a form to a record, from a request to a booking, from an idea to something people can use. Creator connects those pieces. It is the shared software engine we build on across Forest of Knowledge.

See how it works Build with Habit Networks

Reusable foundations. Individual products. More room to build what matters.

CreatorFrom information to experience

Give information structureRecords, relationships, and rules

Put it in people's handsForms, views, and connected actions

Build around a real purposeA distinct experience for each product

Seedlings connect the building blocks behind the scenes.

Different products.
Common roots.

A family schedule, a local directory, and a business website serve different people. Each still needs dependable ways to collect information, connect records, recognize users, and turn their choices into actions.

Creator gives us a common foundation for that work. We reuse the underlying capabilities, then shape the language, design, and behavior around each product. Improvements can be carried into other projects through reviewed updates, while each website keeps its own configuration and release.

Inside Creator

The working parts of a useful product.

These capabilities can be combined around what a website needs to do, from a simple intake form to a connected scheduling experience.

Connected information

Define the records a product needs and how they belong together: a business and its locations, an event and its attendees, or a person and their requests. Required fields, relationships, and validation give that information a consistent structure.

Forms that fit the task

Turn those definitions into ways to enter and manage information. Text fields, dates, choices, uploads, and related records can work together in one form, with labels and behavior tailored to the people using it.

A connection to the data

Creator generates APIs from the same definitions that describe the records. An API is how an interface asks to read or save information. Keeping the definitions connected helps the form and the underlying data follow the same rules.

Accounts and permissions

Sign-in, sessions, and access rules connect actions to the right people. A website can distinguish between a visitor, a member, and an administrator, and apply its own rules to what each person can see or change.

Calendars and scheduling

Bring together availability, time zones, invitations, and meeting workflows. Creator includes calendar and booking capabilities; Forest's meeting scheduler uses them for choosing a time, confirming by email code, and managing a booking.

Files alongside the work

Handle uploads and their metadata alongside the records they support. A document, image, or other media file can become part of a product's workflow, with storage and access configured for that website.

Meet the Seedlings

Small definitions.
Connected possibilities.

A Seedling is a reusable definition of a model, form, or interface element. It describes what a piece of the product is and how it should work. Creator uses these definitions to connect the information being stored with the interface people use.

Our team and agents work with Seedlings behind the scenes. You can stay focused on what you want your website to do.

Models describe the information.: A meeting has a time, an organizer, and attendees. A model describes those fields, their relationships, and the rules for saving them.
Forms make it usable.: A form brings the right fields together for a task, such as sending a request or updating a profile.
Elements give it behavior.: Reusable controls, such as date fields, choices, and file uploads, supply the ways people interact with that form.

Already part of Forest

One meeting.
Many connected pieces.

Our meeting scheduler is a practical example of Creator at work. What feels like choosing a time connects availability settings, a verified account, a booking record, and the tools to manage it afterward.

See the Forest scheduler

Set the availability
The host chooses meeting types, a time zone, weekly hours, and date exceptions. Booking opens only when the host enables it.
Find a time that fits
Visitors see available times in their selected time zone. Meeting length, buffers, and existing bookings help determine which times can be offered.
Confirm the booking
An email code verifies the visitor before confirmation. The booking connects the selected time, the host, and the attendee.
Keep plans up to date
Signed-in visitors can view their bookings, reschedule, or cancel. The booking and calendar workflow stay connected as plans change.

How it fits together

The engine.
The collaboration.
The experience.

Creator: The software foundation underneath: connected definitions, interfaces, accounts, and reusable capabilities.
Habit Networks: Where you work through a website idea with our team and AI tools, follow the work, and review changes.
The Forest of Knowledge products: The experiences people come to use, with their own purpose, design, and features. Creator lets us develop common foundations while giving each product room to be itself.

Building with us

Start with a conversation.
Keep shaping the result.

Your starting point is Habit Networks. Tell us who your website is for and what you want people to be able to do. The team and agents handle how those ideas connect to Creator underneath.

Describe the useful thing.
“Let customers request an appointment.” “Give members a place to update their details.” Start with a real task and the people who need to complete it.
Review something concrete.
Work through the design and behavior with the team. Use previews and the existing conversation to give feedback, clarify the details, and check that the result fits.
Build on what you learn.
Review changes as the website grows. Shared capabilities can be reused, while custom fields, interfaces, and behavior are developed for your particular website.

A little more
under the surface.

Do I need to learn Seedlings to get started?

No. Start by describing the experience you want in Habit Networks. Seedlings, schemas, and development tools are part of how our team and agents implement it behind the scenes.

Is Creator a separate app I need to sign into?

Creator is the engine included beneath the website or product. Habit Networks is the customer entry point for building with us, and each finished product provides its own experience. Creator's development tools support the work behind that experience.

Can my website have its own features?

Yes. A website can extend shared definitions, add its own records, and customize interface behavior. Changes for one website are kept in that website's own configuration and code, while improvements to the common foundation follow a separate review.

Does every product include every capability?

No. Each product uses the capabilities selected, configured, and released for its purpose. Features that need email, storage, or another service also depend on that website's setup. We work through those requirements as part of the project.

What technology is underneath?

Creator uses structured JSON definitions called Seedlings to generate database structures, APIs, and interfaces. It runs within the host website's Cloudflare application, with services for relational data, file storage, and caching. Website-specific extensions let the shared engine support different experiences.

Bring an idea

What would you like people to be able to do?

A booking flow, a member area, a directory, or something specific to your work. Start the conversation with Habit Networks, and let's shape the experience together.

Meet Habit Networks

Explore Forest of Knowledge