CORE TECHNOLOGYBusiness application platform
FormLogic
A self-hostable platform for forms, business applications, customer portals and visual workflows.
INDEPENDENT SOFTWARE DEVELOPMENT
Business software.
Built to connect.
From the app your team uses to the engine underneath it. F2i develops connected business platforms, local AI tools and portable runtimes.
Six core technologies. Clear responsibilities. Your choice of starting point.
THE F2I ECOSYSTEM06 / CONNECTED TECHNOLOGIES
From interface
to infrastructure.
to infrastructure.
BUSINESS WORKSPACEFormLogicApps, records & workflows
FormLogicApps, records & workflowsAPP CREATION
SoftNPortable interfaces
SoftNPortable interfacesLOCAL CAPABILITY
OAIYAI, services & flows
OAIYAI, services & flowsDistinct roles. Deliberate connections.
A role map, not a requirement to install every project.
Business-focused building blocks Portable application source Local AI options Inspectable technology
THE CORE PORTFOLIO
The right tool.
The bigger picture.
Each project solves a distinct problem. Together, they connect app creation, business operations and local capabilities.
View all projectsCORE TECHNOLOGYCORE TECHNOLOGYPortable application platform
SoftN
A portable app language, visual builder and runtime for editable web and desktop applications.
CORE TECHNOLOGYLocal AI and workflow orchestration
OAIY
A visual workflow builder and local execution layer for models, services, provider connections and device plugins.
CORE TECHNOLOGYPhone and voice integration
Aokie
A local-first AI receptionist that connects a supported mobile phone to OAIY and FormLogic business workflows.
CORE TECHNOLOGYEmbedded execution engine
ZIPP
A Rust JavaScript engine with native and WebAssembly execution, plus experimental Python and browser GPU compute.
CORE TECHNOLOGYLocal application data
XDB
A Rust SQLite record store with Tauri integration, React hooks and an experimental native peer synchronisation path.
Open-source, source-available and proprietary projects are labelled individually. Understand the licensing differences.
START WITH THE WORKSPACE
One record.
More ways to work.
Build a customer portal, a staff application and an administrator view around shared FormLogic forms. Different experiences, without disconnected copies of the data.
Use SoftN when the interface needs to be more specialised. Add OAIY when the workflow needs local AI or devices.
Discover FormLogicSHARED-DATA WORKFLOW
01Intake
Customer portal
Capture a request.
02Operations
Staff workspace
Review and move the work forward.
03Insights
Management view
Understand what needs attention.
Shared forms & records FormLogic
Illustrative workflow. Roles and permissions are configured for the app.
BUILT AROUND REAL NEEDS
Start with the problem.
A useful application does not need every layer. These approaches show which projects belong in the work you want to do.
Explore solutionsBusiness applications
Share records across customer portals, staff tools and operational workflows.
Explore the approachLocal AI & automation
Connect models and local services to a process you can inspect and repeat.
Explore the approachPhone & front desk
Bring call events, transcripts and appointment requests into one workspace.
Explore the approachPortable app development
Build an editable app and choose the runtime and data model that fit.
Explore the approachCONNECTED, NOT COUPLED
A complete ecosystem.
Not a compulsory stack.
FormLogic owns the business workspace. SoftN supplies the app experience. OAIY connects local capabilities. ZIPP, XDB and Aokie each have a specific role underneath.
Understand the architectureBEYOND THE CORE
Room for exploration.
Research and complete applications put the technology to work in different ways. Their experimental scope stays explicit.
Explore the wider portfolioNeural Automata
A local research lab for cellular memory and causal byte-language models, with native PyTorch execution and browser visualisation.
Explore projectSoftN Examples
Tools, simulations, games and emulator experiments that demonstrate the SoftN runtime through complete editable applications.
Explore projectThe Night Window
A voiced observation-horror game built as an editable SoftN application, with a branching campaign and a seeded endless queue.
Explore projectLast Sound
A voiced first-person 3D narrative game for SoftN, demonstrating simulation, checkpoints, spatial interaction and timed audio.
Explore projectUNDERSTAND THE TECHNOLOGY
A little context goes a long way.
Practical guides to choosing a project, understanding local data and planning a deployment.
All resourcesGUIDE 01
Which F2i project should you start with?
Begin with the problem you want to solve. Add the other layers only when the application actually needs them.
Read the guideGUIDE 02
Local-first data, sync and backup boundaries
Local persistence, synchronisation, authentication and backup are separate design decisions.
Read the guideGUIDE 03
Self-hosting and runtime boundaries
Choose where each part runs, what it can access and how it recovers before exposing the application to users.
Read the guideBUILD SOMETHING THAT FITS
Find your starting point.
Explore the platform, the local capabilities or the engine. You do not need the entire stack to do something useful.