Metadata-driven undo is described. In an embodiment, a metadata repository stores metadata that is associated with operations. Attributes associated with each operation are also stored in the metadata. Each operation is associated with an undolet that includes instructions for generating undo entries for operations of a particular operation type. Undo log entries are generated using the metadata and the undolet when a request is intercepted that includes an undoable operation. When an undo command is issued, the instructions in the undo log that are associated with a particular business transaction are executed to “rewind” the transaction.