> For the complete documentation index, see [llms.txt](https://docs.devin.fm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devin.fm/introduction/devin-vs-otto.md).

# Devin vs Otto

If you’ve been working with FileMaker for a while, you know OttoFMS raised the bar for deployment automation. They made deployments and data migrations a lot safer, faster, and less stressful—something that changed the way a lot of us work. OttoFMS still shines when it comes to flexibility and handling more complex deployment workflows, which is a big win if you have unique project needs or need something beyond the basics.

Devin builds on that foundation and takes things further by bringing every stage—development, testing, and delivery—together in one workflow. You still get the reliable deployment and data migration features, but you also get an isolated workspace where you and your team can safely develop and experiment. Saving versions with clear, helpful notes is easy, so everyone can see what changed and who did what. You can track changes in files down to actual code changes in scripts and custom functions, try out ideas on separate branches, and run test scripts right from within Devin before you put anything live. It all adds up to a smooth, modern way to manage the entire lifecycle of your FileMaker apps, whether you’re working on your own or as part of a bigger team.

<figure><img src="/files/Tczu0H4RIrNJnQrFCSD7" alt=""><figcaption><p>Otto vs Devin in DevOps coverage</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devin.fm/introduction/devin-vs-otto.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.