Site map

Every page of the site, by kind: the industries, the modules, the pages, the news and the docs.

Industries 3

  • The software for garagesPhoto inspection, quotes approved by text, the lifts’ planning, calls with the customer’s file on screen, follow ups and reminders that run alone: one app for your garage, made for you and changed when you ask. GoLocomotive is in private testing. Access is by invitation.
  • The software for leisure vehicle dealersMotorhomes, campervans and caravans: one app for your dealership, from the sales floor to the workshop, made for your company and changed when you ask. GoLocomotive is in private testing. Access is by invitation.
  • The software for heating, plumbing and air conditioning firmsService contracts, the technicians' planning, jobs on the phone, quotes and invoices, parts: one app for your heating, plumbing or air conditioning firm, made for you and changed when you ask. GoLocomotive is in private testing. Access is by invitation.

Modules 19

  • The modulesWebsite, forms, customers and deals, quotes and invoices, campaigns, texts, phone, work orders, photo inspection, planning, stock, supplier orders, adverts, rentals, warranty: the modules of your app, and what every app has from day one.
  • The workflow engineWhen a quote is signed, an order is ready or a service date comes near, your app tells the right person, sends the mail and updates the record. Each run reads in words.
  • Catalogue and configuratorYour makers’ price lists in your app, every model with its options, packs and margin, a configurator that checks the configuration, and the quote written with nothing retyped. GoLocomotive is in private testing. Access is by invitation.
  • SMSYour customers’ texts in your app: one thread per customer with their mails, templates, tracked links, consent and STOP honoured, automatic follow ups. GoLocomotive is in private testing. Access is by invitation.
  • Work orders and workshopThe repair order or the job, its lines and who pays each, the parts reserved, the customer’s approval by a link, the technicians’ clocking and the workshop board. GoLocomotive is in private testing. Access is by invitation.
  • WebsiteYour business’s website, served by your app: your pages, your stock live, a page for each item for sale, your forms, your own domain name. You change your words and photos; a new section, you ask us for it. GoLocomotive is in private testing. Access is by invitation.
  • Supplier ordersSupplier orders sent from the app, received in one gesture with their back orders, the supplier’s invoice checked against what came in, and the factory order book. GoLocomotive is in private testing. Access is by invitation.
  • Quotes and invoicesQuotes in lines, invoiced in one act, invoices numbered without a gap, payments and what is left to pay, deposits and credit notes, a PDF in your colors. GoLocomotive is in private testing. Access is by invitation.
  • PlanningPeople, bays and vehicles over the week, bookings moved with the mouse and never booked twice, absences asked and approved, the load of each one. GoLocomotive is in private testing. Access is by invitation.
  • Tracked goodsEach good followed one by one: what blocks its sale or its delivery, what it cost, its covers, its signed reports. GoLocomotive is in private testing. Access is by invitation.
  • FormsForms in your colors, on your site, by a link or a QR code: contact, test drive request, parts request. Each answer arrives in your app, and the legal mention sits under every form. GoLocomotive is in private testing. Access is by invitation.
  • Stock and advertsThe stock for sale published on your listing sites and your website, withdrawn everywhere the day it is sold, the AI’s text confirmed by a person, and the parts counted move by move. GoLocomotive is in private testing. Access is by invitation.
  • Campaigns and consentsWrite to the customers it concerns, only to those who said yes: segments counted again each time they open, the consent register with its proof, the reach before sending and the mail as the customer will read it. GoLocomotive is in private testing. Access is by invitation.
  • Warranty claimsWarranty claims sent to the maker or the insurer, on the cover that held on the day of the failure, with its contract, chased, granted line by line, and the acceptance rate. GoLocomotive is in private testing. Access is by invitation.
  • RentalsBook a category on dates, never more than the fleet, rates by season, departure and return on a signed report, the deposit, the extra kilometres and the invoice. GoLocomotive is in private testing. Access is by invitation.
  • Customers and dealsYour customers, suppliers and partners in one file, the deals on a board by stage, the leads nobody follows and everything late, chased by the app. GoLocomotive is in private testing. Access is by invitation.
  • Photo inspectionThe vehicle inspection on the workshop tablet: point by point in green, orange or red, with photos and videos; the customer answers each recommended job from a link; declined work comes back at the next visit. GoLocomotive is in private testing. Access is by invitation.
  • The journalWho changed what and when in your app, the before and after of each field, and every sign in, in your app’s words. GoLocomotive is in private testing. Access is by invitation.
  • PhoneYour business phone in your app: the caller’s file on screen, each call with its recording, transcript and summary, and an AI agent that answers when nobody can. GoLocomotive is in private testing. Access is by invitation.

Pages 10

  • How it worksFrom your request to a live change: an AI agent builds it, you review it as a card next to the running app, and you decide when it ships.
  • PricingEvery GoLocomotive project is priced on quote. You see a working first version before any price. How a quote works, and what every app comes with.
  • AboutWhat GoLocomotive is, who builds it, why it is built this way, and where it stands today.
  • Access by invitationGoLocomotive is in private testing, and access is by invitation. What that means, and what happens once you are invited.
  • Security and ownershipYour app runs alone: its own process, database and system user, behind five layers. Its code and data are yours, and leave with you. What is not done yet, said plainly.
  • Your app’s assistantAn assistant in your software: it answers from your app’s data, proposes the changes, and a person of your team decides. GoLocomotive is in private testing. Access is by invitation.
  • Connect your AIYour app can act as an MCP server: the AI assistant you already use reads and changes your data as you, under the same rules as the screens.
  • The management software for your tradeThe management software for your trade, adapted to your company and changed when you ask, by our AI agents. GoLocomotive is in private testing. Access is by invitation.
  • Legal notice and privacyWho publishes this site, what it keeps about you, and what is not published yet.
  • Site mapEvery page of the site, by kind: the industries, the modules, the pages, the news and the docs.

News 36

Docs 58

  • What is GoLocomotiveThe management software that adapts to your business. Each client gets its own app, made from a template for its trade and changed by our AI agents on request.
  • Start hereWhat you get, the management software for your trade made into your own app, and what happens between your first message and an app your team uses every day.
  • Trades and presetsThe template each trade starts from, made of ready modules and the trade's own words, three worked examples, and what happens when your trade is not covered yet.
  • Getting startedYour first app, from the template for your trade to the first version your team signs in to.
  • How it worksWho does what between your request and your live app: you, the agents, the shared toolkit, and us.
  • Your first weekGood first requests, how to write a request an agent gets right the first time, and the habits that keep the app clean.
  • Using the portalThe one page where you ask for changes, judge them next to the running app, add modules, release, deploy, and manage users, deployments and settings.
  • Ask for a changeSend a request with your words and a picture of the screen, and follow it until a card answers it.
  • Review a changeRead a card, compare before and after, mark what is wrong, and give the answer that tells the agent what to do next.
  • Release and deployTurn approved changes into a numbered version, put it live, go back one version, or take the app offline.
  • DeploymentsOne app running for several companies of a group, for a test copy, or for a client of yours: each deployment with its own address, data, users, settings and branding.
  • Users and accessCreate the accounts of the people who use your app, set their role, switch them off, and copy them to the live app.
  • App settingsYour app's name, color, logo and language, and the live app's address and access, from the gear in the header.
  • What an app can doThe business modules a trade's app is made of, and the parts every app can use from day one: data screens, accounts, the journal, files, email, automation, backups, two languages.
  • ModulesThe ready parts an app is made of, what each one does for your business, and which ones you add in one click from the portal.
  • Lists, records and formsHow your data shows in the app: lists that the server filters and counts, a page per record, forms, related lists, safe deletes and exports.
  • Sign in and accountsHow people sign in to your app, how a second step protects sensitive roles, and what a user can change on their own account.
  • The journalA record of every change and every sign in: who, when, from where, and each field before and after.
  • Files and emailAttachments on records, private files behind short lived links, file storage off the server, and the emails your app sends.
  • AutomationWhat your app does on its own: values computed on each change, checks before a save, tasks on a schedule, actions behind a button, calls to other services.
  • BackupsA full copy of your app's data at one moment, made on a schedule or on demand, kept off the server in our shared storage, and restored in about a second.
  • Not available yetWhat GoLocomotive does not do today, so you can plan around it. Each item is a plain no, not a promise of a date.
  • Connect your AIYour app as an MCP server. The AI you already use reads and changes your data as you, under the same rules as the screens.
  • Set up your AI clientConnect Claude Code with a token, or a connector such as claude.ai or ChatGPT through your app's own sign in page.
  • What your AI can doThe tools your app gives an AI: the same seven for any data, made to read your data's shape, plus the actions your app adds.
  • Keep your AI in boundsThe limits an AI meets in your app: the account's rights, rules that refuse an AI, hidden tools, a write limit, and the journal.
  • TrustWhere your app runs, what protects it, where your data lives, and what keeps the agents inside their limits.
  • SecurityThe five layers between the internet and your app's data, from the network edge to the rule on each record.
  • Your dataWhere your app's data lives, who can reach it, how it is backed up, and how you take it with you.
  • How agents are containedWhat an agent can and cannot reach while it changes your app, how its spending stops, and what it can never do.
  • Extend your appBigger changes: new kinds of data, new screens, new actions, links to other services. How to ask, and what your app is made of.
  • What to ask forFour example requests, from a sales pipeline to equipment booking, and what the agent builds or adapts in your app for each one.
  • Connect other servicesHow your app talks to other systems: outgoing calls to any web API, incoming webhooks, mail through your own server, files in your own bucket.
  • The agent kitThe written rules every agent loads before it touches an app, shipped with the toolkit so they always match it.
  • DevelopersHow a GoLocomotive app is made: locosdk and its modules, schema.ts, the server, the client, the UI and the golo cli.
  • An app, step by stepThe smallest complete app: a schema, a server, a page with a list of orders, and a sign in.
  • Anatomy of an appThe files of an app repo, what each one owns, and the small contract between an app and the host that runs it.
  • Schema as codeschema.ts declares every collection, field, index, view and rule; the types come from it and the database follows it at each boot.
  • Rules and filtersAPI rules decide who lists, views, creates, updates and deletes each record; filters narrow a list; both use PocketBase's filter language, compiled to SQL.
  • Modules in codeWhat a module is in locosdk, how an app installs one (the spread in schema.ts is the install), the recipes behind the portal's one click install, and the catalogue.
  • Server: hooks, routes, cronscreateApp builds the app's server; hooks wrap every write and sign in, custom routes add endpoints, crons run on a schedule, all in plain TypeScript.
  • Client and data layerThe typed fetch client speaks PocketBase's wire; the MobX data layer turns it into observable lists, records and aggregates that the server pages, filters and sums.
  • UI: shell, grids, formslocosdk/ui gives the app its shell, sign in, server paged grids, record cards, the schema form, the guarded delete, the audit journal and the what's new modal.
  • Auth and mailPasswords, codes by email, two factors, password reset, email change, sign in alerts, the rate limit and the mails, all declared in schema.ts.
  • Files, backups and proxiesFile fields on disk or S3, protected files behind short tokens, backups made while the app writes, restores, and the real client address behind a proxy.
  • The MCP serverOne option turns an app into an MCP server, so a client's own Claude or ChatGPT works in the app as that user, under the same rules, hooks and journal as the UI.
  • Review cards and shotsHow an agent shows the client a change as a card with a before and an after, reads the client's verdict, and works through what the client raises, with golo review and golo shot.
  • Changelog and releasesCHANGELOG.md is what an app's users read; one line per visible change, golo release cuts a version, and the app shows what is new after sign in.
  • Coming from PocketBaselocosdk keeps PocketBase's storage, wire and rule language, so a PocketBase app moves with golo schema import and keeps its database as is.
  • ReferenceThe full tables: every HTTP route, the filter syntax, createApp, the hooks, the field types, the golo cli, the MCP protocol and the changelog format.
  • HTTP APIEvery route a GoLocomotive app serves, with its body and its answer; PocketBase's wire shape throughout.
  • Filter syntaxThe full grammar of the language that API rules and list filters share, PocketBase's own, compiled to SQL.
  • createAppEvery option of createApp and every member of the app object it returns.
  • HooksEvery hook of a GoLocomotive app, its event fields and its default action, plus routes, middlewares and the request event.
  • Field typesEvery field builder of locosdk/schema, its options, its TypeScript type, its SQLite column and its MCP input type.
  • The golo cliEvery command of golo, the cli that ships in locosdk and acts on the app repo it runs in.
  • MCP protocol and OAuthThe wire of an app's MCP server: the methods, the headers of each protocol revision, the error codes, the OAuth routes and the tokens.
  • Changelog formatThe grammar of an app's CHANGELOG.md, which the parser checks line by line.

Search the site

Site map