--- title: Travel and Expense Policy description: Remote work, Berlin week, and travel and accommodation expense guidelines at Langfuse. --- # Travel & expense policy _Last updated: 29.08.2026_ Only applies if you are an employee of Langfuse GmbH ## Remote work and hubs Langfuse is open to remote work. We have two hubs, a larger one in Berlin and a smaller one in San Francisco. While you can generally work from home, we believe in the importance of building culture and collaborating in-person regularly. For San Francisco, as of today, we’re still only hiring in person. This is to build a core hub similar to how we have done in Berlin, before dispersing employees across the US. In Berlin, we aim to meet with all European employees every two months, usually in the first week of a month (to align with new starters who all start from the office in their first week(s)). ## Berlin week We gather in Berlin every two months, usually during the week of the first of the month — Monday to Friday. These weeks are dedicated to: - Welcoming and onboarding new joiners - Team planning and cross-functional collaboration - Informal relationship-building and social time Tuesday and Thursday evenings will be loosely blocked for team dinners and team events. You may travel during working hours and do not need to use personal time for your commute to and from Berlin. As such, we will start the week all together with lunch and end after lunch on Friday. ## Expenses Our expense policy in the past has been: “don’t be the reason we need an expense policy” — please be reasonable for a company of our stage. You can talk with Leo or founders when in doubt. ### Travel Please book travel with reasonable advance notice to keep costs down. Aim for the most practical and cost-effective option given your location and travel time. If a ticket seems out of range, please ask your supervisor before booking. ### Accommodation We recommend staying close to the office to make the week as easy and connected as possible. The following options are close to our Berlin office and are a good starting point when looking for accommodation: - **Limehome Berlin** or **Numa** — serviced apartments, flexible and comfortable for a working week. Multiple locations close to the office. - **Hotel Monbjiou** or **Amano Hotels** (there are various close to the office) You are not required to book these specific properties, but they are tried and trusted options. Rates greater than 150€/night require a green light from your manager. ### Booking and invoices Please book your travel and accommodation via Pleo cards and upload the correct invoices addressed to our commercial Langfuse GmbH address ([Oranienburgerstraße 91, 10178 Berlin](/imprint)). Include our VAT ID (DE358330767) if it is a cross-border transaction. More info in [Spending money](/handbook/tools-and-processes/spending-money). --- ## Agent Instructions This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/tools-and-processes/travel-and-expense-policy.md`. ### Querying these docs If the answer is not on this page, query the documentation instead of guessing: - **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question: ```bash curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?" ``` - **Index of every page**: , with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt). ### Before writing Langfuse code - **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results. - **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application. - **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples. - **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .