Custom operational software for fleets, terminals, vessels and wellsites.
Describe the work in plain language. Genwright builds the software on a governed platform that has run industrial operations for twelve years — with the data model, permissions and audit trail already underneath it.
Bring your own Anthropic account. No credit system. Unlimited applications and unlimited field users on every deployment.
What the operator described
Every driver does a pre-trip inspection on paper. I need it on a phone, defects need to open a work order in the shop automatically, and I need to hand an inspector two years of signed records without digging through a filing cabinet.
What Genwright built
- RecordsInspection · Defect · Work Order · Asset · Driver
- Field captureOffline-tolerant mobile form, photos, signature
- AutomationOut-of-service defect opens a work order, pages the shop lead
- RetentionImmutable audit trail, tamper-evident timestamps, PDF export
- AccessDriver · Shop · Safety · Read-only auditor
What the operator described
Gate moves live in a spreadsheet, yard position lives in someone's head, and demurrage disputes take a week because nobody can prove when the box actually moved.
What Genwright built
- RecordsGate Move · Container · Yard Slot · Carrier · Appointment
- Field captureGate tablet, handheld yard check, damage photos
- AutomationDwell clock starts at gate-in; free-time expiry alerts
- EvidenceTime-stamped move history exportable per container
- AccessGate · Yard · Billing · Carrier portal
What the operator described
Every vessel keeps its own logs. Planned maintenance is in one system, the safety records are in binders, and when the auditor comes aboard we spend three days assembling what should already exist.
What Genwright built
- RecordsVessel · Equipment · PMS Job · Defect · Drill · Certificate
- Field captureOnboard entry that syncs when the link returns
- AutomationCertificate expiry and overdue-job escalation by vessel
- EvidenceAudit pack assembled per vessel, per date range
- AccessMaster · Chief engineer · DPA · Shore superintendent
What the operator described
Pumpers text me their morning numbers. I retype them into a spreadsheet. By the time production reporting is done the day is over and the numbers are already a guess.
What Genwright built
- RecordsWell · Route · Daily Production · Downtime · Tank · Run Ticket
- Field captureRoute-ordered pumper entry that works without signal
- AutomationVariance flags against expected rate; downtime coded at entry
- EvidenceEntry-level history for every volume that reaches a report
- AccessPumper · Foreman · Engineering · Accounting
Illustrative scopes drawn from common operational patterns. Your first build starts from your workflow, not a template.
The platform underneath has carried operational load since 2014.
Why does operational software take eighteen months to build?
Because almost none of that time is spent describing the work. It is spent rebuilding the same foundation — users, roles, permissions, audit logging, hosting, backups, mobile sync, security review — that every operational system needs and no operator wants to pay for twice.
Operators running fleets, terminals, vessels and wellsites have been offered two options for a long time. Buy off-the-shelf software and reshape the operation around someone else's assumptions. Or commission custom development, wait a year and a half, and pay again for a foundation that already exists in every other system on the market.
The generation step was never the hard part. What you generate onto is.
Describe the work. Build in the Studio. Pass pre-flight. Launch.
Four steps, in order. Nothing reaches production without clearing the one in front of it.
-
STEP 01
Describe the work
Explain the workflow the way you would explain it to a new hire: who does what, what gets recorded, who signs off, and what an auditor will ask for.
-
STEP 02
Build in the Studio
The Studio turns that description into configuration on the Knomatic platform — records, relationships, roles, screens, mobile forms and automations. You review and revise it in place.
-
STEP 03
Pass pre-flight
Every application is inspected before it can launch: data model integrity, permissions, row-level security, audit coverage, and performance under expected load.
-
STEP 04
Launch to production
The application goes live on governed infrastructure with backups, monitoring and change history. Revisions follow the same route — describe, build, pre-flight, launch.
What sits underneath every Genwright application
Genwright does not generate a new application stack for each customer. It configures the Knomatic platform, which has been running operational workloads for industrial, logistics, maritime and fleet businesses for twelve years.
Governed data model
Records, relationships and constraints are enforced by the platform, not by application code that a generator might get wrong on a Friday afternoon.
Audit trail by default
Who changed what, when, and from where — captured at the platform layer, on every record, without anyone remembering to instrument it.
Field-proven infrastructure
Role-based access, row-level security, offline-tolerant mobile capture, backups and monitoring — already built, already inspected, already carrying load.
An application generated onto a governed platform inherits its security posture. An application generated into an empty repository inherits nothing.
Bring your own Anthropic account. There is no credit system.
Genwright builds through Anthropic's Claude Code, running under your own Anthropic account. You pay Anthropic directly at their published rates. Genwright does not resell AI capacity and does not meter your building in credits.
This matters more than it sounds. Platforms that bundle AI usage into a subscription have an incentive to ration it and a reason to keep the true cost of a build opaque. When you hold the provider account, you see exactly what a build costs, you keep whatever rates you have negotiated, and your ability to iterate is not throttled by someone else's margin.
Your account, your rates
Already have an Anthropic agreement? Keep it. Genwright uses the account you already hold rather than reselling capacity back to you at a markup.
Built on Claude Code
Builders run Anthropic's official Claude Code client, which connects to the Knomatic platform through a governed MCP server. Knomatic sits on the tool side of that boundary.
More providers under evaluation
Anthropic is the supported provider today. Additional model providers are on the roadmap; we would rather name them when they ship than promise them now.
You are not starting from a blank canvas.
Twelve years of production modules run on the Knomatic platform today. Genwright starts from the ones that fit your operation and shapes them to how you actually work — which is why a first build takes weeks rather than a year.
Workforce & compliance
Hire-to-retire, built for high-turnover and contractor-heavy operations.
- Applicant tracking
- Onboarding & document collection
- Integrated background checks
- Credential & certification tracking
- Compliance monitoring & expiry alerts
- Scheduling
- Time & attendance
- Contractor management
- Settlements & pay records
Field operations
Dispatch and the people doing the work, wherever they are.
- Dispatch & work assignment
- Offline-tolerant mobile data entry
- GPS tracking & visibility
- Asset tracking & geolocation
- SMS location links
- Radius-based notifications
- Inventory & parts
- Vendor settlement
Order to cash
From the customer's request to the money arriving.
- Customer portals
- Order intake & distribution management
- Reservations
- Contract management
- Invoicing
- Automated payables & receivables
- Revenue-leak and fraud detection
Safety & environmental
The records a regulator or an insurer asks for.
- E-permitting
- Lockout / tagout
- Mustering
- Inspections & incident records
- Corrective action tracking
- OSHA recordkeeping
Records & oversight
What turns activity into something you can prove.
- Forms digitization & scanning
- Dashboards & analytics
- Real-time reporting
- Enforced audit trail
- Integration to existing systems
- In-app chat
These are starting points, not a product you configure around. A module is where your build begins; what ships is shaped to your workflow, your terminology and your approval chain — then inspected at pre-flight like anything else.
Built for operations where the record has to hold up
Four sectors share the same shape of problem: dispersed field users, regulated recordkeeping, and workflows that off-the-shelf software was never designed around.
Logistics & fleet
Trucking fleets, 3PLs, drayage, yard and warehouse operations.
- Inspections and defect-to-work-order
- Dispatch and load exceptions
- Driver qualification files
Maritime & ports
Vessel operators, terminals, marine services and offshore support.
- Planned maintenance and defects
- Safety management evidence
- Gate, yard and move history
Industrial
Manufacturers, fabricators, shops and field service organizations.
- Work orders and job tracking
- Quality holds and NCR handling
- Asset and spares management
Oil & gas
Upstream operators, midstream terminals and oilfield service companies.
- Daily production and downtime
- Route-based pumper capture
- Tank, ticket and transfer records
Genwright compared to the alternatives you are actually weighing
| Factor | Genwright | Off-the-shelf package | Custom development | AI coding tools |
|---|---|---|---|---|
| Time to first production use | Weeks | Weeks to months, plus process change | Twelve to eighteen months, typically | Days to a prototype; production is a separate project |
| Fits your actual workflow | Yes — built from your description | Partially; you adapt to the product | Yes, at full cost | Yes, until it has to scale |
| Audit trail | Enforced at the platform layer | Varies by vendor | Whatever was specified and budgeted | Only if someone builds and maintains it |
| Who runs the infrastructure | Knomatic platform | Vendor | You, or an integrator on retainer | You |
| Production quality gate | Pre-flight inspection before launch | Vendor release process | Depends on the contract | None by default |
| Changing it later | Describe the change; re-run pre-flight | Feature request or configuration limits | Change order | Regenerate and re-test the surrounding system |
| AI cost model | Your own Anthropic account, at Anthropic's rates | Not applicable | Not applicable | Usually bundled credits or seat metering |
Built for operations that answer to a regulator — including the regulator.
The Railroad Commission of Texas, the state agency with regulatory jurisdiction over Texas oil and gas, pipeline safety and surface mining, runs [APPROVED ONE-LINE WORKLOAD DESCRIPTION — MIKE TO SUPPLY] on the Knomatic platform.
The Railroad Commission of Texas does not endorse, sponsor, approve or recommend vendors. This reference describes a delivered engagement and is published with the agency's written consent.
A certified builder can take an application from blank canvas to production — and prove it.
Most first builds run jointly with a Genwright Certified Builder or a channel partner who knows your sector. Certification is earned in the Studio, verified by pre-flight, and carried publicly.
Common questions about Genwright
What is Genwright?
Genwright is a development platform that turns plain-language descriptions of operational work into production software. Applications are built as configuration on Knomatic's governed backend, which supplies the data model, permissions, audit trail and hosting. Genwright is used by fleet, terminal, vessel, plant and wellsite operators who need custom software without an eighteen-month build.
How is Genwright different from an AI coding tool?
AI coding tools generate novel application code that a team must then secure, host, test and maintain. Genwright generates configuration onto an existing governed platform, so data models, authentication, permissions, audit logging and hosting already exist and are already inspected. The generation step is the same speed; the foundation underneath it is different.
Does Genwright charge for AI usage or sell credits?
No. Genwright has no credit system. Genwright builds through Anthropic's Claude Code running under your own Anthropic account, and you pay Anthropic directly at their published rates. Anthropic is the supported provider today; additional providers are on the roadmap. A managed option is available separately for operators who prefer not to hold their own account.
How long does a first Genwright application take?
A scoped pilot covering two to three core workflows typically runs four weeks from kickoff to a production pre-flight review. Build speed is not the constraint on most projects; security review, procurement and internal approval usually govern the calendar. Genwright compresses delivery, not your buying cycle.
What is pre-flight?
Pre-flight is the quality gate every Genwright application passes before it reaches production. It checks data model integrity, permission and row-level security configuration, audit trail coverage, performance under expected load, and deployment readiness. An application that fails pre-flight does not launch until the findings are cleared.
Do we need developers on staff to use Genwright?
You need someone comfortable working in a technical tool — typically an operations systems lead, an IT generalist, or a partner acting on your behalf. Most first builds are run jointly with a Genwright certified builder or channel partner, with your operations team supplying the workflow knowledge and reviewing the result.
Who owns the application and the data?
You own your operational data. Application configuration built for your operation belongs to your organization under the terms of your agreement, and data export is available in standard formats. Genwright does not claim ownership of the workflows you describe or the records your operation generates.
What happens if we outgrow the first application?
Additional applications are added within the same deployment rather than purchased as separate products, and the platform footprint scales on deployed users or units under management rather than per application. Operators commonly start with one workflow and add adjacent ones over the following quarters.
Bring one workflow. We will scope it honestly.
A scoping call is a working session, not a demo. Describe the workflow currently held together by spreadsheets, paper and text messages. You will leave knowing whether Genwright is the right tool for it, what a first build would cover, and what it would cost.