Skip to content

CONNECTORS

Your programs stay. The work moves.

Replace nothing, migrate nothing. LastOS connects to the programs you work with today, and you delegate the work that sits inside them.

ONE DAY

Eight stations, one working day.

This is what a day in your role looks like today, station by station with the programs it happens in. Switch the state and you see what LastOS prepares at every station and where your Approval falls.

Architect, project lead for work stages 5 to 8, practice with 25 staff

State
  1. 07:45

    Inbox: 40 emails, 6 of them plan changes and 2 questions from site management.

    • Outlookopen API
    • Microsoft Teamsopen API
  2. 08:30

    Check the plan status: IFC export against the fire safety and accessibility checklist.

    • Archicadopen API
    • Revitopen API
    • Excelopen API
  3. 10:00

    Client meeting: minutes, open items, cost status per DIN 276.

    • Microsoft Teamsopen API
    • Word
    • ORCA AVAGAEB/IFC exchange
  4. 11:30

    Finish the bill of quantities for the shell, GAEB export.

    • ORCA AVAGAEB/IFC exchange
    • Excelopen API
  5. 13:30

    On site: defect walk, photos, assignment to trades.

    • PlanRadaropen API
    • Smartphone
    • WhatsApp
  6. 15:30

    Site diary and change order review: three change orders from the general contractor.

    • Excelopen API
    • PDF
    • Outlookopen API
  7. 17:00

    Book hours, prepare the invoice for work stage 5.

    • Excelopen API
    • DATEVopen API
  8. 17:30

    End of day: what was approved, what is still waiting.

SILOS

Separate programs today. One line with LastOS.

Every program keeps its data to itself, and a person carries it from one to the next. LastOS changes nothing about the programs. It connects every group to the same line, and the Entry is built from all of them together.

Separate programs, separate data.

Office and email

  • Outlookopen API
  • Microsoft Teamsopen API
  • SharePointopen API
  • Excelopen API

CAD and BIM

  • Archicadopen API
  • Revitopen API
  • Allplanopen API
  • Vectorworksopen API
  • AutoCADopen API

Tendering and cost

  • ORCA AVAGAEB/IFC exchange
  • California.proGAEB/IFC exchange
  • NOVA AVAopen API
  • SIDOUN GlobeGAEB exchange

Site supervision and defects

  • PlanRadaropen API
  • Daluxopen API

Structural analysis

  • Dlubal RFEMopen API
  • SOFiSTiKopen API
  • mb AECno interface yet

Scheduling

  • Asta Powerprojectopen API
  • MS Projectopen API

Documents

  • Nextcloudopen API
  • DocuWareopen API

INTERFACES

  • open API
  • interface on request
  • standard formats such as GAEB, IFC, OpenImmo, DATEV
  • no interface yet

The status per program comes from our review of the interfaces on September 9, 2026. Without public documentation we do not claim an open API. An interface on request is not shown as a connection, and a program without a known interface remains your program, not a connector. Programs without a label have not been reviewed yet.


ACROSS ROLES

Six areas that concern every business.

Image editing, social media, accounting, HR, documents, and communication belong to every role. These programs stay where they are as well.

  • Image editing

    • Adobe Photoshopopen API
    • Adobe Lightroomopen API
    • Canvaopen API
    • Affinity Photono interface yet
  • Social media

    • LinkedInopen API
    • Meta Business Suiteopen API
    • Hootsuiteopen API
    • Laterno interface yet
  • Accounting

    • DATEVopen API
    • Abacusopen API
    • BMDEDI/XML file exchange
    • Lexware Officeopen API
    • sevDeskopen API
  • HR and payroll

    • Personioopen API
    • HRworksopen API
    • rexx systemsinterface on request
    • Sage HRopen API
    • DATEV LODASopen API
  • Document management

    • SharePointopen API
    • Nextcloudopen API
    • DocuWareopen API
    • d.velopopen API
    • ELOopen API
  • Communication

    • Outlookopen API
    • Microsoft Teamsopen API
    • Zoomopen API
    • WhatsApp Businessopen API
    • Threemaopen API

HOW IT WORKS

Five steps, the same in every program.

  1. Source

    A Source is a connected source system, for example your inbox or your industry software, and it stays where it is.


  2. Record

    A Record is what comes in: an email, a document, or a record from the Source.


  3. Rules

    You set the Rules at the start in sentences; the system follows them for all future work.


  4. Entry

    An Entry is the result of the work, a quote, a review note, minutes, or a report, each with its calculation path.


  5. Approval

    The Approval is the last step, it belongs to a person, and only then does anything leave the building.


ACROSS COMPANY BOUNDARIES

The Entry travels from house to house.

When both sides use LastOS, the Entry travels with its audit trail from house to house, from the architecture practice to the general contractor, to the developer, to property management.

Every station records who decided when and on what basis, and nothing is migrated.

Without LastOS on the other side, email remains the connector, and the Entry goes out as a draft that you have approved.

From the plan change to property management

DEMO

See it on a program you know.

In 30 minutes we show you a case from your day-to-day, connected to a program you work with today. You see the Record, the Entry, and the Approval.