Atomic

Atomic runs your code as functions: you name the ones you want to expose in your Driftfile, and Atomic builds them, gives each a URL and secures it. Your source stays ordinary source — there's no framework to learn, no decorator to remember and no server to configure. Write a function, declare it, deploy it.

Start here

• Write a functionThe handler shape, and what you pay for.
• Six languagesGo, Python, Node, Ruby, PHP and Rust.
• Declaring a functionEvery field on an atomic.functions entry.

Reaching a function

• AuthenticationThe auth gate, and per-route API keys.
• Request headersWhat reaches your handler, and what does not.
• TriggersQueue-triggered and scheduled functions.
• StreamingSSE and WebSocket from one function.

Running in production

• Outbound egressWhat a slice may dial, and what it may not.
• Memory and concurrencyWhat a booking buys, and what happens at the edge of it.
• Limits and alertsTimeout, memory and rate, and being told.
• ElementsOne language, one manifest, many functions.
• The CLI surfaceEvery drift atomic command.